Schema viewer searching for a data analytics platform

ABSTRACT

A method for analyzing data from data sources includes receiving user selection of a data source and displaying an interface that includes a schema region and a search box. Each data field in the schema region is associated with a respective system-defined object from the data source. The method also includes receiving user input in the search box. The user input includes a predefined contiguous string of characters specifying a search parameter. The method also includes, in response to the user input in the search box, filtering the data fields displayed in the schema region, thereby displaying only data fields whose data type matches the data type specified by the search parameter.

RELATED APPLICATIONS

This application is related to U.S. application Ser. No. 16/944,047,filed Jul. 30, 2020, entitled “Analyzing Data Using Data Fields fromMultiple Objects in an Object Model,” which is incorporated by referenceherein in its entirety.

This application is related to U.S. application Ser. No. 16/944,056,filed Jul. 30, 2020, entitled “Using Objects in an Object Model asDatabase Entities,” which is incorporated by reference herein in itsentirety.

TECHNICAL FIELD

The disclosed implementations relate generally to analyzing data fromdata sources, and more specifically to analyzing data using datavisualizations constructed according to data fields from multipleobjects in an object model.

BACKGROUND

Data visualization applications enable a user to understand informationin a database visually, including distribution, trends, outliers, andother factors that are important to making business decisions. In somecases, it is necessary for a user to access information from differentdata sources or tables to build a data visualization or create a customcalculation. For example, a large database may include hundreds orthousands of distinct tables or views, and it is frequently necessary tocombine many of the tables in order to get a desired result. In somecases, a user's analysis requires access to more than one database(e.g., one or more tables in an SQL database and also data stored in aspreadsheet or CSV file). When there are many objects, it can bedifficult for a user to find or access the right data.

Some data visualization applications provide a user interface thatenables users to build data visualizations and perform calculations.However, when using data from more than one object or table in thedatabase, information regarding relationships between the objects may berequired, or the tables may need to be joined in order to generate a newdata set that includes data from multiple tables needed for a datavisualization.

In some cases, users do not know how the data from the tables will beused and thus may not be able to specify join types in anticipation ofwhat questions can or will be asked from the data. Thus, the technicalproblem of using data from multiple objects or tables to build a datavisualization or calculation can be particularly challenging.

SUMMARY

Analyzing data from multiple data sets can be challenging. In somecases, it can help to organize the data as an object model. By storingrelationships between different data sets in a database as an objectmodel, relationships between data sets can be leveraged to assist usersanalyzing the data.

An object is a collection of named attributes. An object oftencorresponds to a real-world object, event, or concept, such as a Store.The attributes are descriptions of the object that are conceptually at a1:1 relationship with the object. Thus, a Store object may have a single[Manager Name] or [Employee Count] associated with it. At a physicallevel, an object is often stored as a row in a relational table, or asan object in JSON.

A class is a collection of objects that share the same attributes. Itmust be analytically meaningful to compare objects within a class and toaggregate over them. At a physical level, a class is often stored as arelational table, or as an array of objects in JSON.

An object model is a set of classes and a set of many-to-onerelationships between them. Classes that are related by 1-to-1relationships are conceptually treated as a single class, even if theyare meaningfully distinct to a user. In addition, classes that arerelated by 1-to-1 relationships may be presented as distinct classes ina data visualization user interface. Many-to-many relationships areconceptually split into two many-to-one relationships by adding anassociative table capturing the relationship. Thus, in a hierarchicalobject model, the objects are organized in a hierarchical order based ontheir classes. FIG. 1A provides an example of how a database thatincludes multiple logical tables may be organized in a hierarchicalobject model of object classes. As used herein, an object class istypically referred to as a “data object” or a “data set.” In someimplementations, object model may include different data objects thatare obtained from different databases. For example, a first data objectmay be stored in an SQL database, a second data object may be stored asa desktop file (such as a spreadsheet file or a CSV file), and a thirddata object may be stored in cloud storage. In some instances, a dataobject corresponds almost exactly to a single physical table in adatabase. In some instances, a single physical table in a databasecorresponds to two or more logically distinct data objects that havebeen combined by a union and/or a join.

In some implementations, a user may combine multiple physical tables(e.g., using joins and/or unions) to form one master table. In manycases such a master table is a logical table that is constructed on thefly as needed, but in some cases the master table is materialized asanother physical table (e.g., in a data warehouse). Either way, themaster table can be designated as a single data object. In particular,users can construct new objects from existing objects. Users can alsocreate individual new data fields using data from one or more existingobjects. When defining a new calculated data field, an importantquestion is to determine where the new data field belongs in the objectmodel. As described below, some implementations are able to determinewhere a new data field belongs based on the objects used to create thenew data field and the relations between those objects. For example, ascalar calculation using data fields from a single object creates a newdata field that is a member of the same single object.

Once an object model is constructed, a data visualization applicationcan assist a user in various ways. In some implementations, data fieldsmay be displayed to a user organized hierarchically based on the objectmodel. Alternatively, a data visualization application may present thedata fields to a user based on a user-defined organization scheme, suchas displaying the data fields based on their associations withuser-defined folders. User-defined folders are particularly useful tousers who access the same data sources repeatedly, but access only asmall number of the available data fields.

In some implementations, the data visualization application provides theuser with relevant information, such as identifying which data fieldsare used in a data visualization or calculation, or the number ofrecords from a data object that are used in a data visualization or acalculation. In another example, the data visualization application mayalso identify data fields that are not used in any data visualizationsor calculations.

By allowing the user to use data fields across multiple data sets in adatabase without having to combine the data sets into a single data set,the data visualization application allows users greater flexibility inworking with their data as well as preventing aggregation errors thatcan occur when all of the data objects are combined into a singlemonolithic data set before generating a data visualization. This isexplained in more details in U.S. application Ser. No. 16/246,611, filedDec. 30, 2018, entitled “Generating Data Visualizations According to anObject Model of Selected Data Sources,” U.S. application Ser. No.16/236,612, filed Dec. 30, 2018, entitled “Generating DataVisualizations According to an Object Model of Selected Data Sources,”and U.S. patent application Ser. No. 16/570,969, filed Sep. 13, 2019,entitled “Utilizing Appropriate Measure Aggregation for Generating DataVisualizations of Multi-Fact Datasets,” each of which is incorporated byreference herein in its entirety.

(A1) In accordance with some implementations, a method for analyzingdata from data sources is performed at a computer having one or moreprocessors and memory. The memory stores one or more programs configuredfor execution by the one or more processors. The computer receives userselection of a data source and displays a data visualization userinterface. The data visualization user interface includes a schemaregion, a data visualization region, and a plurality of shelf regions.Each shelf region is configured to define a respective characteristic ofa displayed data visualization according to placement of data fieldsfrom the schema region into the respective shelf region. Each data fieldin the schema region is associated with a respective system-definedobject from the data source. In a first display mode, displaying theschema region includes hierarchically displaying each system-definedobject and the data fields associated with the respective system-definedobject. In the first display mode, the computer receives a user input toswitch from the first display mode to a second display mode. In thesecond display mode, each data field is displayed hierarchically in arespective user-defined folder and the user-defined folders are distinctfrom the system-defined objects. In either the first display mode or thesecond display mode, the computer receives user selection of a firstdata field from the schema region and user placement of the first datafield into a first shelf region. The computer also receives userselection of a second data field from the schema region and userplacement of the second data field into a second shelf region. (Theplacement of the first data field and the placement of the second datafield may be performed in the same display mode or in different displaymodes.) In accordance with placement of the first data field into thefirst shelf region and placement of the second data field into thesecond shelf region, the computer generates and displays a datavisualization in the data visualization region using data for the firstdata field and data for the second data field retrieved from the datasource.

(A2) In some implementations, the computer automatically generates a newdata field that specifies the number of records in a firstsystem-defined data object. The computer also automatically associatesthe new data field with the first system-defined object. In the firstdisplay mode, the computer displays the new data field in associationwith the first system-defined object. The “number of records” data fieldis a calculation that depends on context. The context includes whatfilters are applied. If some rows are being filtered out in a datavisualization, then only the unfiltered rows add to the “number ofrecords.” In addition, the number of records is split based on thevisualization level of detail. For example, if the data is grouped by aRegion data field, then the “number of records” data field computes thecorresponding number of records for each of the Regions.

(A3) In some implementations, in the second display mode, the computerdetects a user gesture (e.g., click or hover) corresponding to the firstdata field. In accordance with detection of the user gesturecorresponding to the first data field, the computer displays thesystem-defined object that is associated with the first data field(e.g., in a popup or tooltip).

(A4) In some implementations, the first data field corresponds to (e.g.,belongs to) a first system-defined object and the second data fieldcorresponds to (e.g., belongs to) a second system-defined object that isdistinct from the first system-defined object. In particular, a user canselect data fields from any of the objects.

(A5) In some implementations, in either the first display mode or thesecond display mode, and in accordance with placement of the first datafield into the first shelf region and placement of the second data fieldinto the second shelf region, the computer automatically joins the firstsystem-defined object with the second system-defined object to retrievedata for the desired data visualization. In some implementations, thecomputer determines a join type between the first system-defined objectand the second system-defined object based on the placement of the firstand second data fields into the first and second shelf regions, and thenthe computer generates a joined table based on the join type. Thecomputer then generates a data visualization based on the joined table.In some implementations, the join type is based on which data fields areselected by the user and the relationships between the data objects inthe object model that connect the selected data fields.

(A6) In some implementations, the first system-defined object is linkedto the second system-defined object through a sequence of one or morerelationships and at least one of the relationships in the sequence ofone or more relationships is a many-to-many relationship. In someimplementations, at least one of the relationships in the sequence ofone or more relationships is a many-to-one relationship

(A7) In some implementations, the computer receives user input to createa calculated data field using a fourth data field belonging to a thirdsystem-defined object. In accordance with the user input to create thecalculation, the computer automatically generates a name and a captionfor the calculation.

(A8) In some implementations, in accordance with receiving the userinput to create a new calculated data field, the computer automaticallyassociates the calculated data field with the third system-definedobject.

(A9) In some implementations, in either the first display mode or thesecond display mode, the computer displays a search box in the schemaregion. The computer receives, in the search box, user input thatincludes a predefined contiguous string of characters that specify aparameter of a search. In response to the user input in the search box,the computer filters the data fields displayed in the schema region,displaying only data fields whose data type matches a data typespecified by the search parameter.

(A10) In some implementations, in the second display mode, the computerreceives user input to associate a fifth data field with a firstuser-defined folder and user input to associate a sixth data field withthe first user-defined folder. The fifth data field is associated with asixth system-defined object, the sixth data field is distinct from thefifth data field, and the sixth data field is associated with a seventhsystem-defined object that is distinct from the sixth system-definedobject. In the second display mode, the computer displays the fifth datafield and the sixth data field in association with the firstuser-defined folder. The computer receives user input to switch from thesecond display mode to the first display mode. In the first displaymode, the computer displays, in the schema region, the fifth data fieldas associated with the sixth system-defined object and the sixth datafield as associated with the seventh system-defined object.

(B1) In accordance with some implementations, a method for analyzingdata from data sources is performed at a computer having one or moreprocessors and memory. The memory stores one or more programs configuredfor execution by the one or more processors. The computer receives userinput to specify a mathematical expression. The mathematical expressionincludes a first data field from a first system-defined object and asecond data field from a second system-defined object. The second datafield is distinct from the first data field. The first object and thesecond object are distinct objects of an object model comprising a treein which each relation between objects represents a respectivemany-to-one relationship between respective objects. The computer thengenerates a calculated data field based on the mathematical expressionand automatically assigns the calculated data field as a member of athird object in the object model according to relations in the treeconnecting the first object to the second object.

(B2) In some instances, the third object is distinct from the firstobject and distinct from the second object.

(B3) In some instances, the tree includes a many-to-one relationshipfrom the third object to the first object and a many-to-one relationshipfrom the third object to the second object, and the third object isdistinct from each of the first object and the second object.

(B4) In some instances, the third object is the same as the first objector the third object is the same as the second object.

(B5) In some instances, the tree includes a many-to-one relationshipfrom the first object to the second object. In such cases, assigning thecalculated data field as a member of the third object in the objectmodel includes assigning the calculated data field as a member of thefirst object.

(B6) In some instances, the mathematical expression includes a thirddata field from a fourth object. The tree includes a many-to-onerelationship from the first object to the second object and amany-to-one relationship from the first object to the fourth object. Insuch cases, assigning the calculated data field as a member of the thirdobject in the object model includes assigning the calculated data fieldas a member of the first object.

(B7) In some instances, the mathematical expression includes a thirddata field from a fourth object, distinct from the first object anddistinct from the second object. The tree includes: 1) a many-to-onerelationship from the third object to the first object, 2) a many-to-onerelationship from the third object to the second object, and 3) amany-to-one relationship from the third object to the fourth object. Thethird object is distinct from each of the first object, the secondobject, and the fourth object.

(B8) In some implementations, assigning the calculated data field as amember of the third object in the object model includes identifying aset of candidate objects. Each candidate object has a respectivesequence of zero or more many-to-one relations in the tree from therespective candidate object to each of the first and second objects.Assigning the calculated data field as a member of the third object inthe object model includes selecting the third object as an object in theset of candidate objects having a smallest total sequence length to thefirst and second objects.

(B9) In some implementations, each of the first object, the secondobject, and the third object belongs to a same data source.

(B10) In some implementations, the computer receives a user selection toinclude the calculated data field in a data visualization and generatesand displays the data visualization according to calculated data valuesfor the calculated data field.

(B11) In some implementations, the computer automatically generates aname and a caption associated with the calculated data field.

(B12) In some implementations, in a first display mode of a userinterface, the computer displays, in a schema region of the userinterface, the calculated data field as belonging to the third object.

(B13) In some implementations, the computer receives, in the firstdisplay mode, a user input to switch from the first display mode to asecond display mode that is different from the first display mode. Inthe second display mode, the computer displays, in the schema region ofthe user interface, the calculated data field as belonging to a defaultfolder.

(B14) In some implementations, in the second display mode, the computerreceives user input to associate the calculated data field with auser-defined folder that is distinct from the default folder. Thecomputer also displays, in the schema region of the user interface, thecalculated data field as belonging to the user-defined folder.

(B15) In some implementations, in the second display mode, the computerreceives user input to associate the first data field with theuser-defined folder and displays, in the schema region of the userinterface, the first data field and the calculated data field asbelonging to the user-defined folder.

(B16) In some implementations, the computer displays a search box in theschema region and receives user input in the search box. The user inputincludes a predefined contiguous string of characters that specify aparameter of a search. In response to the user input in the search box,the computer filters the data fields displayed in the schema region,displaying only data fields whose data type matches a data typespecified by the search parameter.

(B17) In some implementations, the predefined contiguous string ofcharacters includes “C:” and the user input includes the predefinedcontiguous string of characters followed by one or more charactersspecifying a search term. The predefined contiguous string of charactersspecify a search of calculated data fields whose calculation expressionsinclude the search term.

(C1) In accordance with some implementations, a method for analyzingdata from data sources is performed at a computer having one or moreprocessors and memory. The memory stores one or more programs configuredfor execution by the one or more processors. The computer receives userselection of a data source and displays a data visualization userinterface that includes a schema region and a search box. Each datafield displayed in the schema region is associated with a respectivesystem-defined object from the data source. In a first display mode, thecomputer displays the schema region by hierarchically displaying eachsystem-defined object and the data fields associated with the respectivesystem-defined object. The computer receives user input to switch fromthe first display mode to a second display mode. In the second displaymode, each data field is displayed hierarchically in a respectiveuser-defined folder, and the user-defined folders are distinct from thesystem-defined objects. In either the first display mode or the seconddisplay mode, the computer receives user input in the search box. Theuser input includes a predefined contiguous string of characters thatspecify a search parameter. In response to the user input in the searchbox, the data fields displayed in the schema region are filtered suchthat the computer displays only data fields whose data type matches thedata type specified by the search parameter.

(C2) In some implementations, the user input includes the predefinedcontiguous string of characters followed by one or more charactersspecifying a search string. Filtering the data fields displayed in theschema region includes displaying only data fields whose displayed namesinclude the search string.

(C3) In some implementations, the user input includes the predefinedcontiguous string of characters followed by one or more charactersspecifying a search string. The search parameter specifies searching forcalculated data fields. Filtering the data fields displayed in theschema region includes displaying only data fields whose displayed namesinclude the search string or whose corresponding calculation expressionsinclude the search string.

(C4) In some implementations, the data type specified by the searchparameter is one of (i) dimension, (ii) measure, or (iii) calculation.

(C5) In some implementations, receiving the user input in the search boxincludes detecting a user gesture to display a list of predefined searchparameters. In response to detecting the user gesture, the computerdisplays a list of predefined search parameters. In response toreceiving a user selection from the displayed list, the computerautomatically populates the search box with the predefined contiguousstring of characters corresponding to the user selection from thedisplayed list.

(C6) In some implementations, the computer continues to display onlydata fields whose data type matches the data type specified by thesearch parameter in response to receiving the user input to switch fromthe first display mode to the second display mode.

(C7) In some implementations, the schema region includes the search box.

(C8) In some implementations, the computer receives user selection of adata field displayed in the schema region and user placement of theselected data field into a data visualization definition region of thedata visualization user interface. The computer also generates a datavisualization based on the user selection and placement, and displaysthe generated data visualization, including one or more visual markscorresponding to data from the selected data field.

(C9) In accordance with some implementations, a method for analyzingdata from data sources is performed at a computer having one or moreprocessors and memory. The memory stores one or more programs configuredfor execution by the one or more processors. The computer receives userselection of a data source and displays a data visualization userinterface that includes a schema region and a search box. Each datafield displayed in the schema region is associated with a respectivesystem-defined object from the data source. In a first display mode, thecomputer displays the schema region by hierarchically displaying eachsystem-defined object and the data fields associated with the respectivesystem-defined object. The computer receives user input to switch fromthe first display mode to a second display mode. In the second displaymode, each data field is displayed hierarchically in a respectiveuser-defined folder, and the user-defined folders are distinct from thesystem-defined objects. In either the first display mode or the seconddisplay mode, the computer receives user input, in the search box. Theuser input includes (i) a predefined contiguous string of charactersspecifying a search parameter and (ii) a search string. In response tothe user input in the search box and a determination that the searchparameter specifies a first metadata characteristic about data fields inthe data source, the computer filters the data fields displayed in theschema region, displaying only data fields whose first metadatacharacteristic includes the search string.

(C10) In some implementations, the first metadata characteristic storesuser-provided comments about data fields from the data source.

(C11) In some implementations, the computer detects a user gesturecorresponding to a first data field displayed in the schema region, andin response to detecting the user gesture, the computer displays acomment associated with the first data field.

(C12) In some implementations, the schema region includes the searchbox.

In accordance with some implementations, a system for analyzing datafrom data sources includes one or more processors, memory, and one ormore programs stored in the memory. The programs are configured forexecution by the one or more processors. The programs includeinstructions for performing any of the methods described herein.

In accordance with some implementations, a non-transitory computerreadable storage medium stores one or more programs configured forexecution by a computer system having one or more processors and memory.The one or more programs include instructions for performing any of themethods described herein.

Thus methods, systems, and graphical user interfaces are provided foranalyzing data from data sources.

BRIEF DESCRIPTIONS OF THE DRAWINGS

For a better understanding of the aforementioned implementations of theinvention as well as additional implementations, reference should bemade to the Description of Implementations below, in conjunction withthe following drawings in which like reference numerals refer tocorresponding parts throughout the figures.

FIG. 1A illustrates example of an object model representation of amulti-object data source in accordance with some implementations.

FIG. 1B illustrates an example of a data visualization interface in anobject-based display mode in accordance with some implementations.

FIG. 1C illustrates an example of a data visualization interface in afolder-based display mode in accordance with some implementations.

FIG. 2A is a block diagram of a computing device according to someimplementations.

FIG. 2B is a block diagram of a data visualization server according tosome implementations.

FIGS. 3A-3E are block diagrams of object model schemas according to someimplementations.

FIGS. 4A-4F illustrate a graphical user interface in an object-baseddisplay mode according to some implementations.

FIGS. 5A-5E illustrate a graphical user interface in a folder-baseddisplay mode according to some implementations.

FIG. 5F illustrates providing additional information regarding a datafield via a graphical user interface according to some implementations.

FIGS. 6A-6J illustrate features of a graphical user interface accordingto some implementations.

FIGS. 7A-7C illustrate a data object screen according to someimplementations.

FIGS. 8A-8P illustrate analyzing data in a data visualizationapplication according to some implementations.

FIGS. 9A-9G provide a flow chart for a method of analyzing a data sourcewith multiple data objects in accordance with some implementations.

FIGS. 10A-10F provide a flow chart for a method of analyzing a datasource with multiple data objects in accordance with someimplementations.

FIGS. 11A-11B provide a flow chart for a method of analyzing a datasource in accordance with some implementations.

FIGS. 12A-12B provide a flow chart for a method of searching for datafields in a data visualization user interface in accordance with someimplementations.

Reference will now be made in detail to implementations, examples ofwhich are illustrated in the accompanying drawings. In the followingdetailed description, numerous specific details are set forth in orderto provide a thorough understanding of the present invention. However,it will be apparent to one of ordinary skill in the art that the presentinvention may be practiced without these specific details.

DESCRIPTION OF IMPLEMENTATIONS

Some implementations of an interactive data visualization applicationuse an object model 102 to show relationships 106 between data objects104, as shown in FIG. 1A. The data objects 104 that are part of theobject model may be stored locally (e.g., on the same device that isdisplaying the user interface) or may be stored externally (e.g., on adatabase server or in the cloud). In this example, each relationship 106is a many-to-one relationship between two data objects 104 in the objectmodel. (The arrows point from the “one” side of each relationship to the“many” side of the relationship.) The hierarchical structure of theobject model allows the relationships between the data objects 104 inthe object model to be visualized. The object model 102 may also showcharacteristics or data fields that are present in each of the dataobjects 104 and link them to other data fields or characteristics inrelated data objects. The many-to-one relationships between the dataobjects 104 shows the organizational structure of the object model 102.In some instances, each data object corresponds to a database table or adistinct physical file.

Some implementations of an interactive data visualization applicationuse an object model 102 to represent a multi-object data source. In someinstances, an object model 102 applies to one database (e.g., one SQLdatabase or one spreadsheet file), but an object model may encompass twoor more databases. Typically, unrelated databases have distinct objectmodels. In some instances, the object model 102 closely mimics the datamodel of the physical database (e.g., classes in the object modelcorrespond to data sets or tables in a database). However, in some casesthe object model 102 is more normalized (or less normalized) than thephysical data sources. An object model 102 groups together attributes(e.g., data fields) that have a one-to-one relationship with each otherto form classes (data objects 104), and identifies many-to-onerelationships 106 among the classes. In the illustrations below, themany-to-one relationships are illustrated with arrows, with the arrowsoriginating from the “one” side of the relationship and pointing towardsthe “many” side of each relationship. When an object model isconstructed, it can facilitate analyzing data from the data source usingdata fields that are specified or selected by a user. In someimplementations, the data fields correspond to columns in the data set(e.g., in a data table).

In some instances, a user may select data fields from different dataobjects 104 in the object model 102 to be included for analysis. Thedata fields may be added to a graphical user interface that allows theuser to work with the data, such as generating calculated fields andcreating data visualizations. FIGS. 1B and 1C show examples of agraphical user interface for analyzing data in a data source.

FIGS. 1B and 1C show a graphical user interface 140 in an object-baseddisplay mode and a folder-based display mode, respectively, inaccordance with some implementations. The graphical user interface 140includes a schema region 150 (also sometimes referred to as a “schemaviewer”), a plurality of shelf regions 152 (in this example, two shelfregions 152-1 and 152-2 are shown), and a data visualization region 154.Data fields are shown in the schema region 150. In some implementations,the schema region 150 shows data fields that are selected by the user.In some cases, the schema region 150 shows all data fields that are inobject model 102 by default when no data fields are selected by theuser. In some cases, the schema region 150 shows all data fields thatare included in data objects 104 that are selected by the user. Eachshelf region 152 is configured to define a respective characteristic ofa displayed data visualization according to placement of data fieldsfrom the schema region 150 into the respective shelf region 152. Thedata visualization region 154 is configured to display datavisualizations.

As shown in FIG. 1B, in the object-based display mode, each data fieldin the schema region 150 is associated with a respective data object 104of the object model 102. In the object-based display mode, the schemaregion 150 displays each object 104 and the data fields 160 associatedwith the respective object 104 in a hierarchical manner. For example,the data fields “Line Items,” “Order Number,” and “Order date” are allincluded in the “Sales Data” data object 104-1 and thus, are shown inschema region 150 as belonging to the “Sales Data” data object 104-1when the data visualization is in the object-based display mode.

For example, in the object-based display mode, the schema region showstwo distinct data objects 104, a first data object 104-1 correspondingto a data set entitled “Sales Data”, and a second data object 104-2corresponding to a data set entitled “Customer Data.” The data fields160-1 are shown to be associated with (e.g., are included in, are partof, are nested under, belong to) the “Sales Data” object 104-1.Similarly, the data fields 160-2 are shown to be associated with (e.g.,are included in, are part of, are nested under, belong to) the “CustomerData” object 104-2.

Referring to FIG. 1C, in the folder-based display mode, the schemaregion 150 displays the data fields 160 in a respective user-definedfolder 170 in a hierarchical manner. Note that the data fields 160displayed in FIGS. 1B and 1C correspond to the same data fields 160 fromthe same object model. For example, a user may select one or more datafields from a data object 104 to be included in a user-defined folder170. A user-defined folder 170 (e.g., user-defined folders 170-1, 170-2,and 170-3) may include any number of data fields. In some cases, auser-defined folder 170 may include two or more data fields, each ofwhich is associated with a different data object 104 in the object model102. For example, the “Customers” user-defined folder 170-2 includes twodata fields, “Customer Name” from the “Sales Data” object 104-1 and“Customer Name” from the “Customer Data” object 104-2. Thus, any datafield can exist in any folder, allowing users to organize the datafields as they see fit.

As shown in FIG. 1C, in the folder-based display mode, the schema region150 shows 3 distinct user-defined folders, a “Locations” user-definedfolder 170-1, a “Customers” user-defined folder 170-2, and a “Product”user-defined folder 170-3. Data fields 172-1 are shown to be associatedwith (e.g., are included in, are part of, are nested under, belong to)the “Locations” user-defined folder 170-1, data fields 172-2 are shownto be associated with (e.g., are included in, are part of, are nestedunder, belong to) the “Customers” user-defined folder 170-2, and datafields 173-3 are shown to be associated with (e.g., are included in, arepart of, are nested under, belong to) the “Product” user-defined folder170-3. Note that despite the fact that the data field “Location” belongsto the “Customer Data” object 104-2 (as shown in the object-baseddisplay mode in FIG. 1B), in the folder-based display mode, the schemaregion 150 shows that the data field “Location” belongs to the“Locations” user-defined folder 170-1.

FIG. 2A is a block diagram illustrating a computing device 200 (e.g., aclient device) that can execute a data visualization application 222 ora data visualization web application to display a data visualization. Insome implementations, the computing device displays a graphical userinterface 224 for the data visualization application. Computing devices200 include desktop computers, laptop computers, tablet computers, andother computing devices with a display and a processor capable ofrunning a data visualization application 222. The data visualizationapplication 222 may include a data source generator for databaseorganization (e.g., generating object models for databases) as well asgenerating new data sources using existing databases. A computing device200 typically includes one or more processing units/cores (CPUs) 202 forexecuting modules, programs, and/or instructions stored in the memory214 and thereby performing processing operations, one or more network orother communications interfaces 204, memory 214, and one or morecommunication buses 212 for interconnecting these components. Thecommunication buses 212 may include circuitry that interconnects andcontrols communications between system components. A computing device200 includes a user interface 206 comprising a display 208 and one ormore input devices or mechanisms 210. In some implementations, the inputdevice/mechanism includes a keyboard; in some implementations, the inputdevice/mechanism includes a “soft” keyboard, which is displayed asneeded on the display 208, enabling a user to “press keys” that appearon the display 208. In some implementations, the display 208 and inputdevice/mechanism 210 comprise a touch screen display (also called atouch sensitive display). In some implementations, the display is anintegrated part of the computing device 200. In some implementations,the display is a separate display device.

In some implementations, the memory 214 includes high-speedrandom-access memory, such as DRAM, SRAM, DDR RAM or other random-accesssolid-state memory devices. In some implementations, the memory 214includes non-volatile memory, such as one or more magnetic disk storagedevices, optical disk storage devices, flash memory devices, or othernon-volatile solid-state storage devices. In some implementations, thememory 214 includes one or more storage devices remotely located fromthe CPUs 202. The memory 214, or alternatively the non-volatile memorydevices within the memory 214, comprises a non-transitory computerreadable storage medium. In some implementations, the memory 214, or thecomputer readable storage medium of the memory 214, stores the followingprograms, modules, and data structures, or a subset thereof:

-   -   an operating system 216, which includes procedures for handling        various basic system services and for performing hardware        dependent tasks;    -   a communication module 218, which is used for connecting the        computing device 200 to other computers and devices via the one        or more communication network interfaces 204 (wired or wireless)        and one or more communication networks, such as the Internet,        other wide area networks, local area networks, metropolitan area        networks, and so on;    -   a web browser 220 (or other client application), which enables a        user to communicate over a network with remote computers or        devices;    -   a data visualization application 222, which provides a graphical        user interface 224 for a user to construct visual graphics        (e.g., an individual data visualization or a dashboard with a        plurality of related data visualizations). In some        implementations, the data visualization application 222 executes        as a standalone application (e.g., a desktop application). In        some implementations, the data visualization application 222        executes within the web browser 220 (e.g., as a web        application);    -   the data visualization application 222 includes a graphical user        interface 224, which enables a user to build data visualizations        by specifying elements visually, and also provides a graphical        view to access or build object models and data sources;    -   the data visualization application also includes a data        visualization generator 226, which generates data visualizations        according to user specification. In accordance with some        implementations, the data visualization generator 226 generates        a data visualization in accordance with user association (e.g.,        placement) of data fields with respective data shelf regions        152. In some implementations, the data visualization generator        226 generates a data visualization based on characteristics such        as data type (e.g., data characteristics) of a data field that        is selected by the user for inclusion the data visualization;    -   the data visualization application also includes a calculation        generator 228, which generates calculated fields based on        user-defined mathematical expressions. For example, a user may        include one or more data fields in a mathematical expression        that defines a calculated field. Calculated fields can be        treated in the same way as data fields. For example, calculated        fields may be associated with one or more user-defined folders,        calculated fields may also be associated with a data object 104        of the object model 102, and calculated fields may be used in        generating data visualizations;    -   the data visualization application also includes a display mode        module 230 that is responsible for the organization and display        of data fields in the object-based display mode and the        folder-based display mode. In some implementations, the display        mode module 230 allows for smooth transitioning between the two        display modes and updates the schema region 150 based on which        display mode is currently selected (e.g., active). The display        mode module 230 also keeps track of user-defined folders 170 and        associations between data fields and the user-defined folders in        the folder-based display mode;    -   the data visualization application also includes a naming module        232 that is configured to update names for user-defined folders        170, data objects 104, and data fields. In accordance with some        implementations, the naming module 232 is configured to keep        track of naming conventions and naming changes implemented by        the user. In some implementations, the naming module 232 is        configured to automatically rename or generate a new name for a        data field that has a same name as another data field such that        a user can distinguish between, for example, two data fields        entitled “Address,” where the first data field includes delivery        addresses from a first data object 104-1 and the second data        field includes store addresses from a second data object 104-2        that is different from the first data object 104-1;    -   the data visualization application also includes a relationships        module 234 that is responsible for keeping track of the        relationships between data objects 104 of object model 102. In        accordance with some implementations, the relationships module        234 uses the relationship between two or more data objects 104        of object model 102 in order to automatically determine (e.g.,        assign, categorize, discern) which data object 104 a generated        data visualization or a calculated data field belongs to. In        accordance with some implementations, the relationships module        234 uses the relationship between two or more data objects 104        of object model 102 in order to automatically form one or more        joins that are specific to a user-defined calculation or a        user-defined data visualization; and    -   one or more object models 102, which identify the structure of        one or more databases 112. Each object model 102 includes a        plurality of data objects (classes), such as a first data object        104-1 and a second data object. Each object model 102 also        includes many-to-one relationships 106 between the data objects        104. In some instances, an object model 102 maps each data set        or table within a database to a data object 104, with        many-to-one relationships 106 between data objects 104        corresponding to foreign key relationships between the data        sets. In some instances, the model of an underlying database        does not cleanly map to an object model 102 in this simple way,        so the object model 102 includes information that specifies how        to transform the raw data into appropriate data objects 104. In        some instances, the raw data source is a simple file (e.g., a        spreadsheet), which is transformed into multiple data sets        objects (e.g., one data set per worksheet tab). In some        implementations, the object model also includes one or more        many-to-many relationships between objects. Because many-to-many        relationships provide less information about how the objects are        related, some implementations replace each many-to-many        relationship with an additional object (e.g., an associative        table) and many-to-one relationships to the additional object.        This is particularly useful when the associative table        corresponds to a meaningful concept. For example, there is a        many-to-many relationship between Customers and Products for a        store. These two objects are related by transactions in which a        customer buys a specific product, and a transaction is an        important concept on its own, with a sales date, purchase price,        quantity sold, computed sales tax, and other attributes.        Creating a Transactions object and/or a LineItems object can        replace the many-to-many relationship with many-to-one        relationships.

Each of the above identified executable modules, applications, or set ofprocedures may be stored in one or more of the previously mentionedmemory devices, and corresponds to a set of instructions for performinga function described above. The above identified modules or programs(i.e., sets of instructions) need not be implemented as separatesoftware programs, procedures, or modules, and thus various subsets ofthese modules may be combined or otherwise re-arranged in variousimplementations. In some implementations, the memory 214 stores a subsetof the modules and data structures identified above. In someimplementations, the memory 214 stores additional modules or datastructures not described above.

Although FIG. 2A shows a computing device 200, FIG. 2A is intended moreas a functional description of the various features that may be presentrather than as a structural schematic of the implementations describedherein. In practice, and as recognized by those of ordinary skill in theart, items shown separately could be combined and some items could beseparated.

FIG. 2B is a block diagram of a data visualization server 290 inaccordance with some implementations. A data visualization server 290may host one or more databases 286 or may provide various executableapplications or modules. A server 290 typically includes one or moreprocessing units/cores (CPUs) 250, one or more network interfaces 252,memory 260, and one or more communication buses 254 for interconnectingthese components. In some implementations, the server 290 includes auser interface 256, which includes a display 258 and one or more inputdevices 259, such as a keyboard and a mouse. In some implementations,the communication buses 254 include circuitry (sometimes called achipset) that interconnects and controls communications between systemcomponents.

In some implementations, the memory 260 includes high-speedrandom-access memory, such as DRAM, SRAM, DDR RAM, or otherrandom-access solid-state memory devices, and may include non-volatilememory, such as one or more magnetic disk storage devices, optical diskstorage devices, flash memory devices, or other non-volatile solid-statestorage devices. In some implementations, the memory 260 includes one ormore storage devices remotely located from the CPU(s) 250. The memory260, or alternatively the non-volatile memory devices within the memory260, comprise a non-transitory computer readable storage medium.

In some implementations, the memory 260, or the computer readablestorage medium of the memory 260, stores the following programs,modules, and data structures, or a subset thereof:

-   -   an operating system 262, which includes procedures for handling        various basic system services and for performing hardware        dependent tasks;    -   a network communication module 264, which is used for connecting        the server 290 to other computers via the one or more        communication network interfaces 252 (wired or wireless) and one        or more communication networks, such as the Internet, other wide        area networks, local area networks, metropolitan area networks,        and so on;    -   a web server 266 (such as an HTTP server), which receives web        requests from users and responds by providing responsive web        pages or other resources;    -   a data visualization web application 270, which may be        downloaded and executed by a web browser 220 on a user's        computing device 200. In general, a data visualization web        application 270 has the same functionality as a desktop data        visualization application 222, but provides the flexibility of        access from any device at any location with network        connectivity, and does not require installation and maintenance.        In some implementations, the data visualization web application        270 includes various software modules to perform certain tasks.        In some implementations, the data visualization web application        270 includes a user interface module 272, which provides the        user interface for all aspects of the data visualization web        application 270;    -   in some implementations, the data visualization web application        includes a data visualization generator 274, which generates and        displays data visualizations according to user-selected data        sources and data fields, as well as one or more object models        102;    -   in some implementations, the data visualization web application        includes a calculation generator 228, a display mode module 230,        a naming module 232, and a relationships module 234, each of        which is described above for a computing device 200;    -   one or more object models 102, as described above for a        computing device 200;    -   a data retrieval module 284, which builds and executes queries        to retrieve data from one or more databases 286. The databases        286 may be stored locally on the server 290 or stored at an        external database system. In some implementations, data from two        or more different data sources (e.g., databases) may be blended.        In some implementations, the data retrieval module 284 uses a        visual specification to build the queries;    -   one or more databases 286, which store data used or created by        the data visualization web application 270 or data visualization        application 222. The databases 286 may store data sources 288,        which provide the data used in the generated data        visualizations. Each data source 288 includes one or more data        fields 292. In some implementations, the database 286 stores        user preferences. In some implementations, the database 286        includes a data visualization history log 294. In some        implementations, the data visualization history log 294 tracks        each time the data visualization web application 270 or data        visualization application 222 renders a data visualization.

The databases 286 may store data in many different formats, and commonlyincludes many distinct tables, each with a plurality of data fields 292.Some databases 286 comprise a single table. The data fields 292 includeboth raw fields from the database (e.g., a column from a database tableor a column from a spreadsheet) as well as derived data fields, whichmay be computed or constructed from one or more other data fields. Forexample, derived data fields include computing a month or quarter from adate field, computing a span of time between two date fields, computingcumulative totals for a quantitative field, computing percent growth,and so on. In some instances, derived data fields are accessed by storedprocedures or views in the database. In some implementations, thedefinitions of derived data fields 292 are stored separately from thedata source 288. In some implementations, the database 286 stores a setof user preferences for each user. The user preferences may be used whenthe data visualization web application 270 (or desktop datavisualization application 222) makes recommendations about how to view aset of data fields 292. In some implementations, the database 286 storesa data visualization history log 294, which stores information abouteach data visualization generated. In some implementations, the database286 stores other information, including other information used by thedata visualization application 222 or data visualization web application270. The databases 286 may be separate from the data visualizationserver 290, or may be included with the data visualization server (orboth).

In some implementations, the data visualization history log 294 storesvisual specifications selected by users, which may include a useridentifier, a timestamp of when the data visualization was created, alist of the data fields used in the data visualization, the type of thedata visualization (sometimes referred to as a “view type” or a “charttype”), data encodings (e.g., color and size of marks), and the datarelationships selected. In some implementations, one or more thumbnailimages of each data visualization are also stored. Some implementationsstore additional information about created data visualizations, such asthe name and location of the data source 288, the number of rows fromthe data source that were included in the data visualization, theversion of the data visualization software, and so on.

Each of the above identified executable modules, applications, or setsof procedures may be stored in one or more of the previously mentionedmemory devices, and corresponds to a set of instructions for performinga function described above. The above identified modules or programs(i.e., sets of instructions) need not be implemented as separatesoftware programs, procedures, or modules, and thus various subsets ofthese modules may be combined or otherwise re-arranged in variousimplementations. In some implementations, the memory 260 stores a subsetof the modules and data structures identified above. In someimplementations, the memory 260 stores additional modules or datastructures not described above.

Although FIG. 2B shows a data visualization server 290, FIG. 2B isintended more as a functional description of the various features thatmay be present rather than as a structural schematic of theimplementations described herein. In practice, and as recognized bythose of ordinary skill in the art, items shown separately could becombined and some items could be separated. In addition, some of theprograms, functions, procedures, or data shown above with respect to aserver 290 may be stored or executed on a computing device 200. In someimplementations, the functionality and/or data may be allocated betweena computing device 200 and one or more servers 290. Furthermore, one ofskill in the art recognizes that FIG. 2B need not represent a singlephysical device. In some implementations, the server functionality isallocated across multiple physical devices that comprise a serversystem. As used herein, references to a “server” or “data visualizationserver” include various groups, collections, or arrays of servers thatprovide the described functionality, and the physical servers need notbe physically collocated (e.g., the individual physical devices could bespread throughout the United States or throughout the world).

FIGS. 3A-3E are block diagrams of object model schemas according to someimplementations. An object model can be depicted as a graph or blockdiagram, as shown in FIGS. 3A-3E. FIGS. 3A-3E illustrates differenttypes of object models, all of which are supported by the data analysismethods described herein.

FIG. 3A shows an example of a hierarchical object model 300 that isarranged so that the “many” side of each relationship is always to theleft of the “one” side. The many-to-one relationships 306 in the objectmodel 300 are illustrated by arrows, with the arrows originating fromthe “one” side of the relationship and pointing towards the “many” sideof each relationship. The object model 300 includes multiple dataobjects 104, which are referred to individually as a data object 304-nwith n as a placeholder for a data set identifier (e.g., data object304-1 is distinct from data object 304-2). The data objects 304 in theobject model 300 have many-to-one relationships 106, connecting eachdata object 304-n with at least one other data object and forming atree. Thus, the tree structure illustrates different classes (dataobjects) in the object model 300, as well as the many-to-onerelationships 306 between the data objects 304.

For example, the data objects 304-5 and 304-6 each has a directmany-to-one relationship to the data object 304-4. Each of the dataobjects 304-5 and 304-6 can be described as being “upstream” from thedata object 304-4.

In a second example, the data object 304-3 is related to each of thedata objects 304-5 and 304-6 via sequences of two many-to-onerelationships. Thus, the data object 304-3 can be described as being“downstream” from each of the data objects 304-5 and 304-6. Referring tothe relationship between the data objects 304-3 and 304-7, the dataobject 304-7 is not related to the data object 304-3 via a sequence ofmany-to-one relationships or via a sequence of one-to-manyrelationships. Thus the data object 304-7 is not considered to be“upstream” or “downstream” from the data object 304-3. The data object304-7 can be considered to be on a different “branch” of the tree. Inthe same way, the data objects 304-8, 304-9, 304-10, and 304-11, whichare part of the same “branch,” are neither “upstream” nor “downstream”from any of the data objects 304-2, 304-3, 304-4, 304-5, and 304-6,which form a different “branch” on the tree.

FIG. 3B shows an example of a hierarchical object model 310 that isarranged so that the “many” side of each relationship is always to theleft of the “one” side. The many-to-one relationships 316 in the objectmodel 310 are illustrated by arrows, with the arrows originating fromthe “one” side of the relationship and pointing towards the “many” sideof each relationship. The object model 312 includes multiple dataobjects 314 that have many-to-one relationships 316, connecting eachdata object 314-n with at least one other data object and forming atree.

For example, the data object 314-1 has a direct many-to-one relationshipto each of the data objects 314-2, 314-3, and 314-4. Thus, data object314-1 can be described as being “upstream” from each of the data objects314-2, 314-3, and 314-4.

In a second example, the data object 314-8 is related to each of thedata objects 314-3 and 314-1 via sequences of two many-to-onerelationships. Thus, the data object 314-8 can be described as being“downstream” from each of the data objects 314-3 and 314-1.Additionally, when looking at two or more data objects 314, it ispossible that two or more data objects 314 may share one or more commonancestors. For example, data objects 314-1 and 314-3 are commonancestors to the data objects 314-6, 314-8, and 314-10. A least commonancestor is a common ancestor that is separated by the fewest number ofmany-to-one relationships to each of the “descendant” data objects 314.In this example, data object 314-3 is the least common ancestor of dataobjects 314-6, 314-8, and 314-10. In a second example, a least commonancestor of data objects 314-9 and 314-8 is data object 314-7.

FIG. 3C shows an example of a hierarchical object model 320 that includedata objects 324 that have many-to-one relationships 326, connectingeach data object 324-n with at least one other data object and forming atree, similar to object model 310 shown in FIG. 3B. However, objectmodel 320 includes a loop formed by data objects 324-5, 324-6, and324-9. As shown, each of the data objects 324-5 and 324-6 has a directmany-to-one-relationship to data object 324-9. Additionally, data object324-5 also has a direct many-to-one-relationship to data object 324-6.

FIG. 3D shows an example of a star schema object model 330. As shown,object model 330 includes data objects 334 that have many-to-onerelationships 336, connecting each data object 334-n with at least oneother data object. As shown, data object 336-1 has a directmany-to-one-relationship to each of the data objects 334-2, 334-3,334-4, 334-5, and 334-6.

FIG. 3E shows an example of a snowflake schema object model 340. Asshown, object model 340 includes data objects 344 that have many-to-onerelationships 346, connecting each data object 344-n with at least oneother data object. As shown, data object 346-1 has a directmany-to-one-relationship to each of the data objects 334-2, 334-3,334-4, and 334-6. Additionally, the data object 344-4 has a directmany-to-one-relationship to the data object 344-5. Similarly, the dataobject 344-6 has a direct many-to-one-relationship to each of the dataobjects 344-7 and 344-8.

FIGS. 4A-4F show examples a schema region 150 when a graphical userinterface 140 is in an object-based display mode according to someimplementations.

Referring to FIG. 4A, when the object model includes a single dataobject (e.g., an object model that has one data object) and the dataobject includes a single table (e.g., the data object has one table),the schema region 150 shows data fields that are in the data object.Since there is only one data object and only one table in the dataobject, the schema region 150 may, in some cases, not display the dataobject name or a heading (e.g., name, title) for the table.Additionally, the data fields are grouped by whether the data field is aDimension or a Measure. In general, Dimensions are data fields thatgenerally cannot be aggregated (other than by counting). Dimensions aretypically categorical fields, storing data such as names, products,regions, or stores. In contrast, Measures are data fields that can bemeasured, aggregated, or used in mathematical operations (e.g.,computing sums). For example, as shown, the schema region 150 displays(e.g., shows, lists) the data fields grouped based on whether the datafield is a Dimension or a Measure. Data fields that are Dimensions areshown above a line 410 (shown in FIG. 4A as a solid gray line) and datafields that are measures are shown below the line 410.

Additionally, data fields from different data sets may be used to formcalculations (also referred to as calculated field) or to generate adata visualization. In addition to any user-defined parameters, such asa mathematical expression defining a calculation or a user associationof data fields to respective shelf regions, the relationshipsrepresented in the object model can be used to automatically associatethe calculated fields or generated data visualizations to a particulardata object in the object model.

The schema region 150 also includes one or more data fields that areautomatically generated by the data visualization application. In thisexample, the “Number of Records” data field is an automaticallygenerated field.

In some implementations, a generated field (e.g., a user-generated fieldsuch as a calculated field, or an application-generated field such as anumber of records field) is shown below a data field with which thegenerated field is associated. Additionally, in some implementations,the schema region 150 displays generated fields using a text style(e.g., font characteristic) that is different from a text style used todisplay data fields from the data object. For example, as shown,generated data fields are shown in italicized font and data fields fromthe data object are shown in non-italicized font.

Referring to FIG. 4B, when the object model includes a single dataobject and the data object includes multiple tables (e.g., the objectmodel has one data object and the data object corresponds to a pluralityof unionized tables), the schema region 150 shows the data fields in thedata object grouped by the table to which the data field belongs (e.g.,is associated with). Since there is only one data object, the schemaregion 150 may, in some cases, not display the data object name.Additionally, the data fields are grouped by whether the data field is aDimension or a Measure. In this example, the data object has two tables,“Orders” and “Customers,” and a list of data fields associated with eachtable is displayed (e.g. shown, listed) underneath the table heading.Data fields shown above line 410 are Dimensions and data fields shownbelow the line 410 are Measures. As shown, the “Orders” table includesboth Dimensions and Measures. Thus, the “Orders” table is shown onceabove the line 410 with Dimensions listed under the “Orders” heading,and once below the line 410 with Measures listed under the “Orders”heading. For example, the data fields “Line Items” and “Order Number”(among others) are data fields that are Dimensions and belong to the“Orders” table and “Sales” and “Profit” (among others) are data fieldsthat are Measures and belong to the “Orders” table.

FIG. 4C provides additional examples of how a schema region 150 maydisplay data fields when the object model includes a single data object(e.g., an object model that has one data object) and the data objectincludes multiple tables. When an object model includes a plurality ofdata objects (e.g., two or more data objects) and each data objectincludes one table (e.g., a single table, only one table), the schemaregion 150 displays the data fields grouped by the data object to whichthe data field belongs. In some implementations, the schema region 150displays the data object names. In some implementations, the schemaregion 150 may optionally display the table headings (e.g., names).Additionally, the data fields are grouped by whether the data field is aDimension or a Measure. In this example, there are three data objects(e.g., three tables), “Actor,” “Appearance,” and “Character.” The“Actor” data object includes two data fields, “Actor” and “Height.” Auser viewing the schema region 150 is able to quickly determine that thedata field “Actor” is a Dimension and the data field “Height” is aMeasure based on the separation between the two data fields by the line410.

FIG. 4D provides additional examples of how a schema region 150 maydisplay data fields when an object model includes a plurality of dataobjects (e.g., two or more data objects) and at least one of the dataobjects includes multiple tables (e.g., a plurality of tables, two ormore tables), the schema region 150 displays the data fields grouped bythe data object (or table) to which the data field belongs. In someimplementations, the schema region 150 displays the data object names.In some implementations, the schema region 150 may optionally displaythe table headings (e.g., names). Additionally, the data fields aregrouped by whether the data field is a Dimension or a Measure.

For example, under the “Sales Data” data object, the line 410 separatesthe Dimensions and Measures that belong to the “Sales Data” data object.Thus, data fields that belong to the “Sales Data” data object and areDimensions (such as “Line Items,” “Order Number,” “Order Date,” “ShipDate,” “Customer Name,” “Product Name,” and “Top Customer by Profit”)are shown above the line 410, and data fields that belong to the “SalesData” data object and are Measures (such as “Sales,” “Profit,”“Discount,” and “Number of Sales Data Records”) are shown below the line410.

In some implementations, data fields that are not part of a table (e.g.,does not belong to a table) are shown below all the tables (e.g., belowall the tables and the data fields that belong to a table). Examples ofdata fields that may not be associated with a table include generateddata fields, calculated data fields, and number of records data fields.An example is shown in FIG. 4D, where data fields “Measure Names,”“Number of Records,” and “Measure Values” are at the bottom of theschema region 150 and are not shown to belong to or be associated withany data objects or tables. However, a user is able to quickly discernthat the data field “Measure Names” is a Dimension and the data fieldsNumber of Records” and “Measure Values” are Measures since they areseparated by the line 410. Another example is shown in FIG. 4D, wheredata fields “Measure Names,” “Order Size per Customer,” and “Longitude(generated)” are at the bottom of the schema region 150 and are shown asnot belonging to or being associated with any data objects or tables.

In some implementations, as shown in FIG. 4E, data fields that are notassociated with a data object in the object model are listed under a ‘NoObject’ section 420 (e.g., a “common area). In some implementations,data fields that are associated with multiple data objects in the objectmodel (such as complex calculations) are also listed under the ‘NoObject’ section 420. As shown, the data fields in the ‘No Object’section 420 are listed hierarchically and grouped based on whether thedata field is a Dimension or Measure. For example, when a user generatesa new data field (such as a calculated data field) that uses informationfrom two or more data fields belonging to different data objects in theobject model, the new data field may be listed under the ‘No Object’section 420.

Referring to FIG. 4F, a user may switch between the object-based displaymode and the folder based display mode. In some implementations, asshown, the graphical user interface 140 displays an indication (e.g.,check mark) of the active display mode. In this example, a drop downmenu 530 shows that the user is currently in the object-based mode(e.g., “Group by Data Source Object”). The drop down menu 530 alsoprovides the user with an option to select either the object-baseddisplay mode (e.g., “Group by Data Source Object” option) or thefolder-based display mode (e.g., “Group by Folder” option), therebyallowing the user to seamlessly switch between the two display modes.Alternatively, an indication of the active display mode as well asoptions to switch between display modes may be shown as a pop-up.Additionally, the options to switch between display modes may beavailable via an icon or affordance that is part of the graphical userinterface 140. Alternatively, the options to switch between displaymodes may be accessible via one or more user gestures (e.g., a userright click on a portion of the schema region 150).

FIGS. 5A-5E show the schema region 150 when the graphical user interface140 is in a folder-based display mode according to some implementations.

When the graphical user interface 140 is first launched and before anycustom (e.g., user-defined) folders are created, the schema region 150simply lists the data fields in the object model. In someimplementations, the schema region 150 may have one folder that sautomatically generated as a default folder. In some implementations,the default folder is named the same as the data source. In such cases,as shown in FIG. 5A, the data fields are grouped based on whether thedata field is a Dimension or Measure. In some implementations, as shown,the line 410 separates the Dimensions from the Measures.

Referring to FIG. 5B, once one or more user-defined folders are created,the schema region 150 shows the user-defined folders and displays thedata fields that are associated with each user-defined folder. In someimplementations, a user may indicate (e.g., assign, determine) whichdata fields are associated with a specific user-defined folder bydragging and dropping a data field into a desired user-defined folder.In this example, there are three folders, an “Orders” folder, a“Location” folder, and a “Customers” folder. A user has identified thatthe data fields “Line Items,” “Order Number,” “Profit,” and “Discount”(among others) belong to the “Orders” folder and thus, the data fieldsare listed underneath the “Orders” folder heading. Additionally, withina given user-defined folder, the data fields are separated by line 410based on whether the data field is a Dimension or Measure. The schemaregion 150 displays the information so that a user can quickly ascertaininformation regarding this data source. In this example, a user canquickly determine that the data field “Person” is a Dimension thatbelongs to the “Orders” folder, and the “Sales” data field is Measurethat belongs to the “Orders” folder.

The data visualization application 222 allows a user to organize theuser-defined folders and data fields in any manner that he/she sees fit.Thus, any data field can belong to (e.g., be associated with) anyfolder.

In some implementations, there may be one or more data fields that arenot associated with any folder. In such cases, as shown in FIG. 5C, theschema region 150 may display unassociated data fields at the bottom ofthe schema region 150. In this example, the data fields “Line Items,”“Person,” and “Sales,” (among others) are displayed at the bottom of theschema region 150, indicating that these data fields do not belong to auser-defined folder. Additionally, the schema region 150 separates theunassociated data fields using line 410 based on whether theunassociated data field is a Dimension or Measure.

In some implementations, in response to a user gesture regarding a datafield, the schema region 150 may show the data object that the datafield is associated with. For example, FIG. 5D shows an example ofdisplaying the data object that a data field is associated with when auser hovers over the data field. In this example, the user hovers overthe “Product Name” data field that is part of the “Orders” folder. Inresponse to the user hovering a mouse over the “Product Name” datafield, the schema region 150 displays the data object to which the“Product Name” data field is associated (e.g., the “sales data” dataobject, shown in light grey). In another example, FIG. 5E shows that theschema region 150 displays the data object to which the “Customer Name”data field is associated (e.g., the “sales data” data object) inresponse to a user clicking on the “Customer Name” data field.

Thus, when the graphical user interface 140 is in the folder-baseddisplay mode, the schema region 150 allows the user flexibility toorganize data fields into user-defined folders as they see fit.Additionally, the data fields are still connected to the underlyingobject model of the data source and users can quickly and easilydetermine the relationship of data fields to data objects in the objectmodel (e.g., which data object the data field is associated with)without having to switch back to the object-based display mode.

Referring to FIG. 5F, in some implementations, the schema region 150 isconfigured to display additional information 550 regarding a specificdata field in response to a user gesture regarding (e.g., selecting,indicating) the data field. The user gesture may be, for example, any ofa hover, left-click, right click, or press and hold (in the case oftouch sensitive displays). In some implementations, as shown, theadditional information 550 is displayed in the form of a drop down menu.The additional information 550 may include any of: a summary or previewof the information stored in the data field, a number of records in thedata field that are currently used in an data analysis (e.g., acalculation or data visualization), a number of records that arecurrently not used in data analysis (e.g., not used in a calculation ordata visualization), and the names of calculations and/or datavisualizations that utilize information from the selected data field.This functionality of providing additional information 550 regarding aselected (e.g., indicated) data field can be accessed from any of (e.g.,both) the object-based display mode and the folder-based display mode.

FIGS. 6A-6J show features of the graphical user interface according tosome implementations. Once a user selects a data source, the user canadd any data fields or tables from the data source to a workspace orworkbook via the graphical user interface 140 at any point in time.Additionally, the user may generate data visualizations and calculationsin the workspace. The name of a table or data field in the data sourceare referred to herein as “field names” and the name of the table asshown in the graphical user interface 140 and in the user's workspace isreferred to herein as the “remote name” or “local name.” The user may,via graphical user interface 140, change the field name of a table ordata field (including both data fields from the data source anduser-generated data fields). In some implementations, as a default, theremote name of a table or a data field is the same as the field name.However, in some implementations, a data source may include tables ordata fields that have a same name, or a user may add a table afterhaving started performing some analysis (e.g., creating some calculatedfields or data visualizations). Such instances may lead to namingconflicts, which can be automatically handled (e.g., independently ofuser input, without additional user input or intervention) by the datavisualization application 222, described in detail below.

Referring to FIG. 6A, the graphical user interface 14 shows a datapreparation screen for editing (e.g., adding, removing, editing) tablesto a workspace. In this screen, the schema region 150 of displays (e.g.,lists) tables that are included in the data source. In this example, theuser has added (e.g., clicked, double clicked) the “LineItems” table tothe user's workspace. In response to the user selection to add the“LineItems” table to the workspace, a list of data fields from the“LineItems” table is shown in panel 620.

As mentioned above, the user may also change the remote name of a tableonce the table has been added to the workspace. Following the exampleprovided above in FIG. 6A, FIG. 6B shows an example where the user hasdecided to rename the “LineItems” table to “Table A.” In response to theuser changing the remote name of the “LineItems” table to “Table A,” theremote name of the table is automatically updated in the table section610, and data fields shown in the panel 620 are updated to reference“Table A” instead of “LineItems.” However, the schema region 150 shows“LineItems” and not “Table A” since the schema region 150 displays thefield names of tables as they occur in the data source in the datapreparation screen.

Following the example provided above in FIG. 6A, FIG. 6C shows anexample where the user adds a second table, “Orders,” to the workspace.In response to the user selection to add the “Orders” table, the datavisualization application automatically performs a join between the“LineItems” table and the “Orders” table. Additionally, the panel 620 isupdated to show data fields from both the “LineItems” table and the“Orders” table.

In some implementations, two or more tables that are added to theworkspace may include data fields having a same name (e.g., a same fieldname, a same name in the data source). For example, the two tables,“LineItems” and “Orders,” may both include a data field with the fieldname “order ID.” FIG. 6D illustrates how the data visualizationapplication 222 handles such situations. In FIG. 6D, the graphical userinterface 140 shows a workspace screen that includes the schema region150, the data visualization region, 154, and the plurality of shelfregions 152-1 and 152-2. Additionally, the graphical user interface iscurrently in the object-based display mode, evidenced by the grouping ofdata fields based on their association with tables in the object modelin the schema region 150. The schema region 150 shows that the“LineItems” table includes two data fields, “Order ID” and “Product ID,”and that the “Orders” table includes six data fields. One of the sixdata fields in the “Orders” table is “Order ID.” In order todifferentiate between the two “Order ID” data fields, the datavisualization application 222 automatically generates a new remote name(e.g., renames) the “Order ID” data field that is associated with the“Orders” table to “Order ID (Orders)” to differentiate it from the“Order ID” data field that is associated with the “LineItems” table,which is labeled as “Order ID.” In other words, the data visualizationapplication 222 automatically adds a caption to the remote name of thedata field so that the remote name of the data field is changed from“Order ID” to “Order ID (Orders).” In some implementations, the captionis automatically generated based on the table to which the data fieldbelongs. In this example, the “Order ID” data field that is associatedwith the “Orders” table is renamed (e.g., the remote name is changed)since the “Orders” table was added after the “LineItems” table. AlthoughFIG. 6D shows the automatic renaming of the “Order ID” data field whenthe graphical user interface 140 is in the object-based display mode,the automatic renaming may also occur when the graphical user interface140 is in the folder-based display mode. In some implementations, achange in the remote name (e.g., automatic renaming, a user-initiatedname change, user-defined name change) is carried over when switchingbetween the display modes.

FIG. 6D also shows an example of a generated data visualization. In thisexample, the data visualization application 222 has generated a datavisualization that is a bar chart showing a sum of the information inthe “Sales” data field. The shelf region 152-2 shows that a sum of the“Sales” data field is associated with the shelf region 152-2. Thegraphical user interface 140 also shows an expanded window 630 (e.g., apop-up window or drop down window) that allows a user to select fromdifferent data visualization types (e.g., data visualization options,chart types, graph types). In some implementations, window 630 showsdata visualization types that are suggested or recommended by the datavisualization application 222. In some implementations, the datavisualization types may be suggested based on any of: characteristics ofthe data field used in the data visualization (e.g., based on data typeof the “Sales” data field), most popular data visualization types, anduser preference of data visualization types.

FIG. 6E shows an example of generating a calculation (e.g., calculateddata field, user-generated field) that uses data in a data field fromthe data source. In this example, the calculation references the “Sales”data field (e.g., uses information or data from the “Sales” data field).The data visualization application 222 automatically generates a remotename and caption for the calculated data field, in this example“Calculation1.” The calculation refers to the remote names and not thefield names that are in the data source. Thus, if the user updates theremote name of the “Sales” data field to, for example, “New Sales Name,”the “Calculation1” calculated field will show that it references the“New Sales Name” data field.

After the first calculated field is generated and automatically named,the user may choose to rename the calculated field. For example, theuser may rename the “Calculation1” calculated field to “NewCalc.” Insuch cases, as shown in FIG. 6F, all instances of “Calculation1” areupdated (e.g., changed) to “NewCalc.”

FIG. 6F also shows an example of generating a calculation thatreferences a calculated field (e.g., references another calculation). Inthis example, the user generates another calculation that references(e.g., uses information from) the “NewCalc” calculated field. As shown,the data visualization application 222 automatically generates a nameand caption for the new calculated field “Calculation2.” In thisexample, if the “Calculation2” calculated field were generated beforethe name change of the “Calculation1” calculated field, the“Calculation2” calculated field would initially reference the“Calculation1” calculated field, and in response to the name change ofthe “Calculation1” calculated field to “NewCalc,” the “Calculation2”calculated field would be updated to show that it references the“NewCalc” calculated field.

As described above, the user may add new tables to the workspace at anypoint in time. FIG. 6G illustrates an example where the user adds a newtable to the workspace after having started some data analysis. In thisexample, the user has already generated a few calculated fields,“Customer Name,” “Number of Records,” and “Measure of Values” (shown atthe bottom of the schema region 150). After having generated thecalculated fields, the user adds a data field from the data source tothe workspace. The data field has the field name the “Customer Name” inthe data source and thus, the default setting would be for the remotename of the data field to also be “Customer Name.” However, a calculatedfield with the remote name “Customer Name” already exists in theworkspace. In order to resolve this naming conflict and clearlydistinguish (e.g., disambiguate) between the two data fields, the datavisualization application 222 automatically adds a caption to the remotename and provides disambiguation logic in order to assign a uniqueremote name to the data field being added. In this example, the datafield being added is automatically assigned the remote name “CustomerName1.” Note that unlike the previous example provided in FIG. 6D, theadded data field is name given the remote name “Customer Name 1” and not“Customer Name (Customer),” which requires the caption to refer to thefield name of the table or data object to which the data field isassociated. This is because generated field (e.g., user-generatedfields), including calculated fields, do not affect any field name toremote name disambiguation and thus, renaming of generated fields andautomatic naming of generated fields do not reference or affect thefield names of data tables or data fields in the data source.

As described above, in some implementations, the user may change theremote name of a table once the table has been added to the workspace.Following the example provided above in FIG. 6C, FIGS. 6H and 6I show anexample where the user has decided to rename the remote name of the“Orders” table to “Table B.” FIG. 6H illustrates the data preparationscreen of the graphical user interface 140. In response to the userchanging the remote name of the “Orders” table to “Table B,” the remotename of the table is automatically updated in the table section 610, anddata fields shown in the panel 620 are updated to reference “Table B”instead of “Orders.” However, the schema region 150 shows “Orders” andnot “Table B” since the schema region 150 of the data preparation screendisplays the field names of tables as they occur in the data source.

FIG. 6I illustrates the workspace screen of the graphical user interface140. After the remote name of the “Orders” table has been changed to“Table B,” the schema region 150 is updated to reflect the remote namechange. The schema region shows two tables “LineItems” and “Table B”(compared to FIG. 6D, before the remote name is changed, which shows“Orders” instead of “Table B”). Following from the example in FIG. 6D,where the remote name of the “Order ID” data field in the “Orders” tablewas automatically renamed to “Order ID (Orders)”, the field name of thedata field remains unchanged and is not updated to “Order ID (Table B).”This is because the data visualization application 222 updates allremote names in the user workspace to the new name (e.g., “Table B”).However, references to tables use the field names as they occur in thedata source. This allows a user to be able to quickly identify whichdata fields belong to which tables when there are duplicate field namesin the data source. Similarly, when the graphical user interface 140 isin the folder-based display mode, in response to a user gesture (e.g.,hover or click) regarding a data field that is associated with the“Orders” table, the graphical user interface 140 will show textindicating that the data field is associated with the “Orders” table,not “Table B” (e.g., the captions refer to the field names and not theremote names). FIG. 6I also illustrates an example of a datavisualization that utilizes information (e.g., data) from two datafields. As shown, the data visualization uses information from the“Order ID (Orders)” data field, which belongs to the “Orders” table(renamed “Table B”), and the “Sales” data field, which does not belongto any specific table in the object model (a user can derive thisinformation from the schema region 150, which lists the “Sales” datafield in an area (e.g., a ‘No Object’ region) to indicate that the“Sales” data field is not associated with any tables or data objects inthe object model.

In some implementations, the user may change the name of data field oncethe data field has been added to the workspace. FIG. 6J illustrates anexample changing the name of a data field. In this example, the user hasrenamed the “Sales” data field to “Number of Sales.” The schema region150 is updated according and now displays “Number of Sales” as a datafield under the heading “Measures” instead of “Sales” (see FIG. 6I,which shows “Sales” before the name of the data field was changed).Accordingly, the remote name of the data field in the shelf region 152-1is also updated to reflect the remote name change. From a user'sperspective, everything that references the data field “Sales” isupdated to reflect the remote name change so that all previous instancesof the “Sales” data field shown on workspace screen is updated to show“Number of Sales” instead. For example, a calculated field that utilizesthe “Sales” data field would be updated to use the new remote name(e.g., to show that the calculated field utilizes the “Number of Sales”data field). As described above, in some implementations, window 630shows data visualization types that are suggested or recommended by thedata visualization application 222. FIG. 6J shows an example where the‘horizontal bars’ data visualization type is suggested to the user inwindow 630. The data visualization type is recommended based on the “1or more measures” included in shelf region 152-1. The window 630 alsoshows that the ‘horizontal bars data’ visualization type is currentlyselected. This is further evidenced by the horizontal bar chart shown inthe data visualization region 154.

FIGS. 7A-7C and 8A-8P illustrate an example of analyzing data using datavisualization application 222. FIGS. 7A-7C show a graphical userinterface 140 displaying a data source screen and FIGS. 8A-8P show thegraphical user interface 140 displaying a data visualization screen thatallows a user to perform data analysis.

FIGS. 7A-7C show a graphical user interface 140 displaying a data sourcescreen for visualizing an object model according to someimplementations. A data source is represented by an object model thatincludes information regarding the relationship between different datasets (e.g., data objects, tables) within the data source. The datasource screen provides a visual representation 710 (e.g., diagram) ofthe object model that includes the data objects in the object model andhow the data objects relate to one another. FIG. 7A illustrates anobject model that includes 8 different data objects. In this example,each book has one author and thus, the object model shows a 1-to-manyrelationship between the “Author” data object and the “Book” data object(e.g., each book has one author, but each author may have writtenmultiple books). In this example, the user has selected the “Author”data object, and data fields 712 (e.g., columns in the data table) inthe selected “Author” data object are shown. In this example, there areseven data fields 712-1 to 712-7. The data source screen 700 alsoprovides a visual indication of whether a specific data field is a fieldthat was generated by a user (e.g., a user-generated field) in the datavisualization application 222. For example, a line 714-1 above the datafield 712-1 indicates that data field 712-1 is a data field that isextracted or linked from the database corresponding to the “Author” dataobject. In contrast, the absence of a line at position 714-7 above thedata field 712-7 indicates that the data field 712-7 is a user-generateddata field that does not exist in the database. In this example, thedata field 712-7 is a user-generated data field that is a concatenationof the information from two other data fields in the data object: theauthors first name (data field 712-2) and the author's last name (datafield 712-3). While data field 712-7 appears in the “Author” data objectand the object model in data visualization application 222, data field712-7 may not appear in the database from which the “Author” data objectis linked or extracted.

Details regarding the data objects and the relationship between two dataobjects in the object model are also provided. For example, as shown inFIG. 7B, in response to a user gesture (e.g., click, double click,hover) over line 722 which represents the relationship between the“Award” data object and the “Book” data object, the graphical userinterface 140 displays additional information regarding therelationship. In this case, the relationship is between the “Book” and“Award” data objects, the relationship is a many-to-may relationshiptype (e.g., a book may have many awards and a specific award may beawarded to many different books), and that the data field “Title” in the“Book” data object is related to the “Title (Award)” data field in the“Award” data object. In some implementations, as shown, the additioninformation is displayed via a pop-up window 720. In another example,shown in FIG. 7C, in response to a user gesture (e.g., click, doubleclick, hover) over the “Book” data object icon, additional informationregarding the data object is provided. In this case, the additionalinformation shows that the “Book” data object includes two tables thathave been joined together. In some implementations, the additionalinformation is provided in a pop-up window 724. In some implementations,the additional information also provides instructions of additionalgestures that may cause the graphical user interface 140 to display moreinformation. For example, a suggestion or tip is provided in the pop-upwindow 724, “double-click this table to see joins.”

To analyze data from a multi-object data source, the relationships inthe object model are leveraged when performing analysis (e.g.,performing calculations and generating data visualizations) using datafrom the data source. For example, data fields from different data setsmay be used without the user having to join (or define a join typebetween) two different data sets in the data source. This allows therelationships between data objects in the object model to be flexibleand adapt as the user develops their analysis. By using flexiblerelationships in the object model opposed to generating a new table byjoining multiple data sets from the object model, incorrect aggregationsand duplications that may occur when joining data sets are avoided. Forexample, to generate a first data visualization using data fields fromtwo different data objects (e.g., two different physical tables in thedatabase), the relationships between the data objects to which the twodata fields belong is used to determine what type of join should beperformed in order to accurately generate desired data visualization.This process is repeated for each individual analytical step (e.g.,generation of a data visualization or performing a calculation). Thus,two tables may be joined in a first way (e.g., an inner join) for afirst data visualization and the same two tables may be joined in asecond way (e.g., a left join, an outer join), different from the firstway, for a second data visualization that utilizes data fields from thesame two tables. The joined or unionized table generated for the firstdata visualization has no bearing or effect on join performed for thesecond data visualization and vice versa. By leveraging therelationships between objects in an object model to perform joins “asneeded,” the user is not restricted in their data analysis options andcan have confidence in data analysis results.

When working via a data visualization application that provides a userinterface, a user's workspace or workbook may be automatically organizedusing the relationships in the object model. FIG. 8A illustrates thegraphical user interface 140 displaying a workspace screen in theobject-based mode for the data source shown in FIGS. 7A-7C. Thegraphical user interface 140 displays the schema region 150, one or moreshelf regions 152 (e.g., shelf regions 152-1 and 152-2), and a datavisualization region 154. In the object based mode, data fields arelisted underneath the data object to which they belong in the schemaregion. FIG. 8B illustrates a zoom in of the schema region 150 in theobject-based mode. As shown in FIGS. 8A and 8B, all data fields(including data fields that are automatically generated by the datavisualization application 222) that belong to the “Author” data objectare listed under the “Author” table heading. Similarly, all data belongto the “Book” data object are listed under the “Book” table heading.Additionally, the data fields are categorized based on whether the fieldis a Dimension or a Measure. Data fields that are Dimensions are shownabove the line 410 and data fields that are Measures are shown belowline 410.

Additionally, the data visualization application 222 may automaticallygenerate one or more data fields corresponding to a data object of theobject model. In this example, the data fields “Author (Count),” “Book(Count),” and “Checkouts (Count)” are automatically generated by thedata visualization application 222. In response to a user gesture (e.g.,click, double click, hover) over the “Author (Count)” data field, thegraphical user interface displays information regarding thesystem-generated data field (e.g., application-generated data field). Inthis example, the “Author (Count)” data field is an automaticallygenerated data field that provides a number of records (e.g., number ofrows) that are in the “Author” data object. Further, thesystem-generated data field is automatically associated with the dataobject to which they are providing a count of a number of records. Asshown in FIGS. 8A and 8B, the “Author (Count)” data field isautomatically associated with the “Author” data field and thus, listedunderneath the “Author” data field. Similarly, the “Book (Count)” datafield is automatically associated with the “Book” data field and thus,listed underneath the “Book” data field. In some implementations, datafields, calculations, and/or data visualizations that are generated(e.g., user-generated, or automatically generated by the datavisualization application 222) may be automatically associated with aparticular data object in the object model based on the relationships inthe object model.

In some implementations, the data visualization application 222automatically generates a count data field for every data object in theobject model. In some implementations, the data visualizationapplication 222 automatically generates a count data field for a subset,less than all, of the data objects in the object model. In someimplementations, in response to a change in the information in the dataobject, the count data field corresponding to the object isautomatically updated. For example, if a new author is added to the“Author” data object, the “Author (Count)” data field would beautomatically updated to reflect the new number of records in theAuthor” data object. These system-generated data fields can be used inthe user's analysis, such as in generating calculations and datavisualizations.

FIG. 8C illustrates switching from the object-based mode to thefolder-based mode. In some implementations, in response to a usergesture (e.g., right click in the schema region 150, selection of icon810), the graphical user interface 140 displays a pop-up window or dropdown menu 540 that includes options for the user to switch to thefolder-based mode (e.g., by selecting the “Group by Folder” option). Inresponse to a user selection to switch to the folder-based mode, theschema region 150 is updated to show data fields based on theirassociation with user-defined folders, as shown in FIG. 8D. In thefolder-based mode, the user can group any data fields (includingsystem-generated data fields) from any data object in the object modelinto user-defined folders. In this example, the user has grouped thefields “AuthorID (Author)” (from the “Author” data object”) “AuthorName,” “Award (Award)” (from the “Award” data object), and “CheckoutMonth” into a same folder that is currently named “Folder 1.” The otherdata fields in the data object (such as the “Auth ID” data field and the“Birthday” data field) are displayed in schema region 150 as not beingassociated with any user-defined folders.

FIGS. 8D-8K illustrate an example of performing data analysis using datavisualizations generated from the object model. As shown in FIG. 8D, auser has associated the “Edition (Count)” data field with the firstshelf region 152-1 (shown abbreviated in the shelf region 152-1 as“CNT(Edition)”) and associated the “Title” data field with the secondshelf region 152-2. In order to generate the resulting datavisualization, displayed in data visualization region 154, the datavisualization application 222 performs a join between the “Edition(Count)” data field from the “Edition” data object and the “Title” datafield from the “Book” data object. The data visualization application222 uses the one-to-many relationship between the “Book” data object tothe “Edition” data object (e.g., one book can have many editions) todetermine and perform a left join between the “Book” data object to the“Edition” data object in order to generate the displayed datavisualization. By performing a left join, the data visualization willinclude any books that may not have a listed edition and thus, no booksare accidentally dropped from the data visualization. In other words,the data visualization application 222 automatically aggregates the“Edition (Count)” data field by the “Title” data field. The left joinperformed between the “Book” data object and the “Edition” data objectis specific for generating this data visualization and does not changethe object model or the relationships between the data objects in theobject model.

Referring to FIG. 8F, in response to a user selection of an icon 820,the data visualization displays a numerical value corresponding to eachvisual mark (e.g., bar) displayed in the data visualization.

Referring to FIG. 8G, in response to a user selection of an icon 822,the data visualization displays the visual marks in order based on thenumber of editions each title (e.g., book) has. In some implementations,in response to a second user selection of the icon 822, the datavisualization displays the visual marks in reverse-order, based on thenumber of editions each title (e.g., book) has.

Referring to FIG. 8H, in response to a user gesture (e.g., click, doubleclick, hover) over a visual mark, the data visualization displaysinformation corresponding to the visual mark. In this example, inresponse to a user hovering their mouse over a visual mark, the datavisualization displays a pop-up window 824-1 that shows that the visualmark corresponds to a book with the title “Zero over Twelve” and thatthat title has 2 editions.

Referring to FIG. 8I, the user has generated a new data visualization byassociating the “Edition (Count)” data field with the first shelf region152-1 (shown abbreviated in the shelf region 152-1 as “CNT(Edition)”)and associating the “Author Name” data field with the second shelfregion 152-2. In order to generate the resulting data visualization,displayed in data visualization region 154, the data visualizationapplication 222 aggregates the “Edition (Count)” data field by the“Author Name” data field. The aggregation performed between the “Author”data object and the “Edition” data object is specific for generatingthis data visualization, different and distinct from the aggregationdescribed above with respect to FIG. 8E, and does not change the objectmodel or the relationships between the data objects in the object model.The resulting data visualization shows a number of book editions thateach author has. In response to a user hover over a visual mark,information corresponding to the visual mark is displayed in a pop-upwindow 824-2.

By performing aggregating the data as described, the data visualizationwill include any authors that may not have a listed edition and thus, noauthors are accidentally dropped from the data visualization. FIG. 8Jshows the data visualization displayed in a rank order. As shown,multiple authors (e.g., Wendell Barton, Robert Milofsky, etc.) that donot have any book editions are included in the data visualization andnot accidentally dropped.

Referring to FIG. 8K, the schema region 150 includes a search box 830(e.g., search bar, search field). The search box 830 is accessible inboth the object-based display mode and the folder-based display mode.The search box 830 is configured to perform incremental search, as shownin FIG. 8K. In this example, the user has typed in “au” and the schemaregion 150 is updated to only display data fields that include theletters “au” in their data field name. In this example, the graphicaluser interface 140 is in the object-based mode and thus, the searchresults are shown grouped under the data object to which they belong. Inthe folder-based mode, the search results are shown grouped under thefolder to which they belong (e.g., have been associated with).

Referring to FIG. 8L, the schema region 150 also includes a searchfilter icon 832. In response to a user selection (e.g., click, doubleclick, hover) over the search filter icon 832, a plurality of filteroptions 834 are displayed (e.g., via a pp-up window or drop-down menu).The data visualization application 222 includes a filter search functionthat allows the user to filter search results by category. For example,search results can be filtered to show only data fields that are acalculation, only data fields that are a Dimension, only data fieldsthat are a Measure, and/or only data fields that include comments.Additionally, the filter search function includes predefined sets ofcharacters that can be used as shorthand in order to implement thesearch filter function when using the search box 830. For example, asshown in FIG. 8M, the user types in a predefined set of characters,“C:”, that correspond to a filter by calculations function, in thesearch box 830. In response to the user input of “C:”, the schema region150 is updated to show only data fields that are calculations. Further,if the user were to type in “C: ID”, the schema region 150 will showonly data fields that are calculations and include the characters “ID”in the data field name. In another example, shown in FIG. 8N, the usermay type “F: certifi” in the search box 830, and the schema region 150will only display data fields that include the characters “certifi” inthe comments. In this example, a user gesture (e.g., click, doubleclick, hover) over the “isbn” data field shows that the “isbn” datafield includes a comment “certified ISBN.”

FIGS. 80 and 8P illustrate an example of data visualization that isgenerated using a calculation. FIG. 8O shows a data visualizationgenerated based on the association of the “Sales (Count)” data fieldwith the first shelf region 152-1 and the association of the “Title” and“Isbn” data fields with the second shelf region 152-2. In order togenerate the data visualization shown in the data visualization region154, the data visualization application aggregates the “Sales (Count)”data field (which represents a number of sales) by the “Title” and“Isbn” data fields. The resulting data visualization displayed in the indata visualization region 154 shows how many sales were made for eachbook title and ISBN. However, if a user wanted to know how much moneywas made rather than how many books were sold (since not all books arepriced the same), the user may include a calculation in the shelfregion. As shown in FIG. 8P, the user may edit a data field in the shelfregion to include a calculation. In this example, the user hasassociated a calculation with the first shelf region 152-1. Thecalculation defines a data field that provides a total sum of the priceof the book multiplied by the number of sales. Thus, the datavisualization application aggregates the calculated field over booktitles and ISBNs in order to generated the displayed data visualization.Since there are two data fields associated with the first shelf region152-1, the data visualization region 154 shows two bar charts: the leftbar chart indicating a number of sold books by title and ISBN and theright bar chart showing a total sales value (in dollars) by title andISBN.

FIGS. 9A-9G provide flow charts of a method 900 of analyzing data fromdata sources in accordance with some implementations. The method 900 isperformed (901) at a computer system having one or more processors andmemory that stores one or more programs configured for execution by theone or more processors. The method 900 includes receiving (902) userselection of a data source and displays (903) a data visualization userinterface 140 (e.g., a graphical user interface 140) that includes aschema region 150, a data visualization region 154, and a plurality ofshelf regions 152 (e.g., shelf regions 152-1 and 152-2). Each shelfregion 152 is configured to define a respective characteristic of adisplayed data visualization according to placement of data fields fromthe schema region 150 into the respective shelf region 152. Each datafield in the schema region 150 is associated with a respectivesystem-defined object from the data source. In a first display mode(e.g., object-based display mode), displaying the schema region 150includes hierarchically displaying each object and the data fieldsassociated with the respective object. The method 900 also includesreceiving (904) user input to switch from the first display mode to asecond display mode (e.g., folder-based display mode) in which each datafield is displayed hierarchically in a respective user-defined folder.The user-defined folders are distinct from the system-defined objects.The method 900 also includes, in either the first display mode or thesecond display mode, receiving (905) user selection of a first datafield from the schema region 150 and user placement of the first datafield into a first shelf region 152-1, and receiving (905) userselection of a second data field from the schema region 150 and userplacement of the second data field into a second shelf region 152-2. Thesecond data field is different (e.g., distinct) from the first datafield and the second shelf region 152-2 is different (e.g., distinct)from the first shelf region 152-1. In accordance with placement of thefirst data field in the first shelf region and placement of the seconddata field into the second shelf region, the method 900 also includesgenerating (906) and displaying (906) a data visualization in the datavisualization region 154 using data from the first data field and thesecond data field retrieved from the data source. An example ofswitching between the first and second display modes is provided withrespect to FIG. 4F (e.g., see user selection of the “Group by Folder”option in the drop down menu 530 in order to switch from an object-baseddisplay mode to a folder-based display mode).

In some implementations, the method 900 also includes automaticallygenerating (910) a new data field that specifies a number of records ina system-defined object, automatically associating (912) the new datafield with the system-defined object, and displaying (914), in the firstdisplay mode, the new data field in association (e.g., as beingassociated) with the system-defined object. For example, the computermay automatically generate an application-generated field (e.g., a“number of records” data field as shown in FIG. 4A) in response to afirst data field being associated with a first system-defined object.The application-generated field is automatically associated with thesystem-defined object and is displayed in the schema region 150 of theuser interface 140 as being associated with the first system-definedobject.

In some implementations, the method 900 includes detecting (920), in thesecond display mode, a user gesture (e.g., single-click, double-click,hover) corresponding to the first data field. In accordance withdetection of the user gesture corresponding to the first data field, themethod 900 includes displaying (922) a system-defined object that isassociated with the first data field. An example is provided in FIG. 5D,where in response to a user gesture (in this example, a hover)corresponding to the “Product Name” data field (that is associated withthe “Orders” user defined folder), the user interface 140 displays, inthe schema region 150, the system-defined object to which the “ProductName” data field belongs (e.g., the “sales data” system-defined object).

In some implementations, the method 900 also includes, in either thefirst display mode or second display mode, detecting (940) a usergesture corresponding to the first data field. In accordance withplacement of the first data field into the first shelf region 152-1 andplacement of the second data field into the second shelf region 152-2,the method also includes automatically joining (940) the firstsystem-defined object with the second system-defined object.Automatically joining (940) the first system-defined object with thesecond system-defined object includes: (i) determining (942) a join typebetween the first system-defined object and the second system-definedobject based on the placement of the first and second data field intothe first and second shelf regions 152-1 and 152-2, and (ii) generating(944) a joined table based on the join type. An example of performing ajoin “as needed” is provided with respect to FIG. 8D.

In some implementations, the first data field corresponds (945) to afirst system-defined object and the second data field corresponds to asecond system-defined object that is distinct from the firstsystem-defined object.

In some implementations, the first system-defined object is linked (946)to the second system-defined object through a sequence of one or morerelationships and at least one of the relationships in the sequence ofone or more relationships is a many-to-many relationship.

In some implementations, the method 900 also includes generating (948) adata visualization based on the joined table.

In some implementations, the method 900 further includes receiving (950)user input to create a calculation (e.g., a calculated field) using afourth data field belonging to a third system-defined object. Inaccordance with receiving the user input to add the calculation, themethod 900 also includes automatically generating (952) a name and acaption for the calculation. In accordance with receiving the user inputto add the calculation, the method 900 also includes automaticallyassociating (954) the calculation with the third system-defined object.

In some implementations, the method 900 also includes, in either thefirst display mode or the second display mode, displaying a search box830 in the schema region 150 and receiving (962) user input in thesearch box 830. The user input includes one or more predefinedcharacters that specify a parameter of a search. The method 900 alsoincludes filtering (964) the data fields displayed in the schema region,displaying only data fields whose data type matches a data typespecified by the search parameter. Examples of receiving user input thatincludes one or more predefined characters (such as “C:”, “D:”, “M”, and“F:”) are provided in FIGS. 8L-8N.

In some implementations, the method 900 includes, in the second displaymode, receiving (970) user input to associate a fifth data field thatbelongs to (e.g., is associated with) a sixth system-defined object to afirst user-defined folder. The method 900 also includes receiving (972)user input to associate a sixth data field to the first user-definedfolder. The sixth data field is associated with a seventh system-definedobject that is distinct from the sixth system-defined object (e.g., thefifth data field and the sixth data field each belong to (e.g., are eachassociated with different system-defined objects). The method 900further includes displaying (974), in the second display mode, the firstdata field and the sixth data field as being associated with the firstuser defined folder. The method 900 also includes receiving (976) userinput to switch from the second display mode to the first display modeand displaying (978), in the schema region 150 while in the firstdisplay mode, the fifth data field as associated with the sixthsystem-defined object and the sixth data field as associated with theseventh system-defined object. An example of switching between the firstand second display modes is provided with respect to FIG. 4F (e.g., seeuser selection of the “Group by Folder” option in the drop down menu 530in order to switch from an object-based display mode to a folder-baseddisplay mode).

FIGS. 10A-10F provide flow charts of a method 1000 of analyzing datafrom data sources in accordance with some implementations. The method1000 is performed (1010) at a computer system having one or moreprocessors and memory that stores one or more programs configured forexecution by the one or more processors. The method 1000 includesreceiving (1020) user input to specify a mathematical expression thatincludes a first data field from a first object (e.g., a firstsystem-defined object, first data object) and a second data field from asecond object (e.g., a second system-defined object). The second datafield is distinct from the first data field. The first object and thesecond object are distinct objects of an object model 102 that includesa tree in which each relation between the objects 104 (e.g., objects104-1 and 104-2) represents a respective many-to-one relationshipbetween respective objects. The method 1000 also includes generating(1030) a calculated data field (e.g., a calculation) based on themathematical expression. The method 1000 further includes assigning(1040) the calculated data field as a member of (e.g., belonging to) athird object (e.g., a system-defined object) in the object model 102according to relations (e.g., relationships) in the tree connecting thefirst object to the second object. FIG. 6E provides an example ofgenerating a calculated data field (e.g., calculation).

In some implementations, the third object is (1042) distinct (e.g.,different) from each of the first object and the second object.

In some implementations, third object is (1044) the same as the firstobject or the second object.

In some implementations, the tree includes (1046) a many-to-onerelationship from the third object to the first object and a many-to-onerelationship from the third object to the second object. The thirdobject is distinct from each of the first object and the second object.

In some implementations, the tree includes (1048) a many-to-onerelationship from the third object to the first object. The calculateddata field is assigned as a member of the first object.

In some implementations, the mathematical expression includes (1050) athird data field from a fourth object (e.g., a system-defined object).The tree includes a many-to-one relationship from the first object tothe second object, and a many-to-one relationship from the first objectto the fourth object. The calculated data field is assigned as a memberof the first object.

In some implementations, the mathematical expression includes (1052) athird data field from a fourth object that is distinct from each of thefirst object and the second object. The tree includes a many-to-onerelationship from the third object to the first object, a many-to-onerelationship from the third object to the second object, and amany-to-one relationship from the third object to the fourth object. Thethird object is distinct from each of the first object, the secondobject, and the fourth object.

In some implementations, each of the first object, the second object,and the third object belongs (1054) to the same data source.

In some implementations, the method 1000 further includes identifying(1060) a set of candidate objects. Each candidate object has arespective sequence of zero or more many-to-one relations in the treefrom the respective candidate object to each of the first and secondobjects. The method 1000 selects (1062) the third object as an object inthe set of candidate objects that has the smallest total sequence lengthto the first and second objects.

In some implementations, the method 1000 includes receiving (1070) userselection to include the calculated data field in a data visualization,and generating (1072) and displaying (1072) the data visualizationaccording to the calculated data values for the calculated data field.An example of a data visualization that uses a calculated data field isprovided with respect to FIGS. 80 and 8P.

In some implementations, the method 1000 further includes automaticallygenerating (1074) a name and a caption that is associated with thecalculated data field. An example is provided in FIG. 6E, where the datavisualization application 222 automatically generates the name“Calculation1” for the calculated data field. For example, referring toFIG. 6E, a name and caption, “Calculation1,” is automatically generatedfor the calculated data field.

In some implementations, the method 1000 further includes, in a firstdisplay mode (e.g., object-based display mode) of a user interface 140(e.g., a graphical user interface 140), displaying (1080) the firstcalculated field as belonging to the third object (e.g., system-definedobject), in a schema region 150 of the user interface 140. The method1000 also includes receiving (1081), in the first display mode, a userinput to switch from the first display mode to a second display mode(e.g., folder-based display mode) that is different from the firstdisplay mode. The method 1000 also includes, in the second display mode,displaying (1082), in the schema region 150, the calculated data fieldas belonging to a default folder, and receiving (1083) a user input toassociate the calculated data field with a user-defined folder that isdistinct from the default folder. An example of switching between thefirst and second display modes is provided with respect to FIG. 4F(e.g., see user selection of the “Group by Folder” option in the dropdown menu 530 in order to switch from an object-based display mode to afolder-based display mode). An example of automatically associating acalculated field with a default folder (e.g., “No Object” section 420)is provided with respect to FIG. 4E.

The method 1000 also includes displaying (1084), in the schema region150 of the user interface 140, the calculated data field as belonging tothe user-defined folder, and in the second display mode, receiving(1085) user input to associate the first data field with theuser-defined folder. The method 1000 also includes displaying (1086), inthe schema region 150 of the user interface 140 while in the seconddisplay mode, the first data field and the calculated data field asbelonging (e.g., being associated with) the same user-defined folder.

In some implementations, the method 1000 further includes displaying(1090) a search box 830 in a schema region 150, and receiving (1092)user input in the search box 830. The user input includes a predefinedcontiguous string of characters that specifies a parameter of a search.In response to the user input in the search box, the method filters(1094) the data fields displayed in the schema region, displaying onlydata fields whose data type matches a data type specified by the searchparameter. Examples of receiving user input that includes one or morepredefined characters (such as “C:”, “D:”, “M”, and “F:”) is provided inFIGS. 8L-8N.

In some implementations, the predefined contiguous string of charactersincludes (1093) “C:” and the user input includes the predefinedcontiguous string of characters followed by one or more characterscorresponding to a search term. In some implementations, “C:” is aparameter that designates searching for calculated data fields (“D:”designates dimensions, “M:” designates measures, and “F:” designatessearching comments). The predefined contiguous string of characters(“C:”) specifies searching only calculated data fields. In this case,filtering the data fields displayed in the schema region comprises(1096) displaying only calculated data fields whose field names containthe search term or whose calculation expressions include the searchterm.

An example of searching using the predefined contiguous string ofcharacters “C:” is provided with respect to FIG. 8M. Another example ofa user input in the search box 830 that includes the predefinedcontiguous string of characters followed by one or more characterscorresponding to a search term is provided with respect to FIG. 8N wherethe predefined contiguous string of characters is “F:” and the one ormore characters corresponding to a search term is “certifi” andcorresponds to (e.g., is at least a part of, is at least a subset of)the search term “certified”. The only data fields display are calculateddata fields that include the term “certifi”.

FIGS. 11A-11B provide flow charts of a method 1100 of analyzing datafrom data sources in accordance with some implementations. The method1100 is performed (1110) at a computer system having one or moreprocessors and memory that stores one or more programs configured forexecution by the one or more processors. The method 1100 includesreceiving (1120) user selection of a data source, and displaying (1130)a data visualization interface 140. The data visualization interface 140includes a schema region 150 and a search box, and each data fielddisplayed in the schema region 150 is associated with a respectivesystem-defined object from the data source. In a first display mode(e.g., object-based display mode), displaying the schema region includeshierarchically displaying each system-defined object and the data fieldsassociated with the respective system-defined object. The method 1100also includes receiving (1140) user input to switch from the firstdisplay mode to the second display mode (e.g., a folder-based displaymode). In the second display mode, each data field is displayedhierarchically in a respective user-defined folder, and the user-definedfolders are distinct from the system-defined objects. The method 1100further includes receiving (1150), in either the first display mode orthe second display mode, user input in the search box 830. The userinput includes a predefined contiguous string of characters specifying asearch parameter. The method 1100 also includes, in response to the userinput in the search box 830, filtering (1160) the data fields displayedin the schema region 150, thereby displaying (1160) only data fieldswhose data type matches the data type specified by the search parameter.An example is provided with respect to FIG. 8M where the search box 830includes a predefined contiguous string of characters, “C:”, whichspecifies a search parameter resulting in displaying only data fieldsthat are calculations.

In some implementations, the data type specified by the search parameteris (1132) one of: (i) dimension, (ii) measure, or (iii) calculation.

In some implementations, the schema region 150 includes (1142) thesearch box 830. FIG. 8N illustrates a schema region 150 that includesthe search box 830.

In some implementations, the user input includes (1162) the predefinedcontiguous string of characters followed by one or more charactersspecifying a search string, and the search parameter specifies searchingfor calculated data fields. The method 1100 filters (1162) the datafields displayed in the schema region, displaying only data fields whosedisplayed names include the search string or whose correspondingcalculation expressions include the search string. An example isprovided with respect to FIG. 8N where the search box 830 includes apredefined contiguous string of characters, “C:”, that specify a searchparameter such that the search results display only data fields that arecalculations, and one or more characters specifying a search string,“certifi.”

In some implementations, the method 1100 further includes continuing todisplay (1170) only data fields whose data type matches the data typespecified by the search parameter, even as the display mode changes. Asshown in FIG. 8M, the data fields, such as “Author Name,” “BookID 2,”“Sales by edition,” “Sales price by edition,” “Sales (pre-discount),“Sales Actual,” and “Sales discounted,” that shown in schema region 150are data fields whose data type matches the data type specified by thesearch parameter. In this example, the predefined contiguous string ofcharacters specifies that the data type is a calculation (e.g., the datafield is a calculated data field). Thus each of the data fieldsdisplayed in the schema region 150 are data fields that are calculations(e.g., are calculated data fields).

In some implementations, the method 1100 further includes receiving(1180) user selection of a data field displayed in the schema region 150and user placement of the selected data field into a data visualizationdefinition region (e.g., a shelf region 152) of the data visualizationuser interface 140.

In some implementations, the method 1100 further includes (1182)generating a data visualization based on the user selection andplacement. An example of generating a data visualization using acalculated field is provided with respect to FIG. 8P.

In some implementations, the method also includes (1184) displaying thegenerated data visualization, including one or more visual markscorresponding to data from the selected data field. An example ofgenerating a data visualization using a calculated field is providedwith respect to FIG. 8P.

FIGS. 12A-12B provide flow charts of a method 1200 of analyzing datafrom data sources in accordance with some implementations. The method1200 is performed (1210) at a computer system having one or moreprocessors and memory that stores one or more programs configured forexecution by the one or more processors. The method 1200 includesreceiving (1220) user selection of a data source, and displaying (1230)a data visualization interface 140. The data visualization interface 140includes a schema region 150 and a search box, and each data fielddisplayed in the schema region 150 is associated with a respectivesystem-defined object from the data source. In a first display mode(e.g., object-based display mode), the user interface displays theschema region hierarchically, displaying each system-defined object andthe data fields associated with the respective system-defined object.The method 1200 also includes receiving (1240) user input to switch fromthe first display mode to a second display mode (e.g., a folder-baseddisplay mode). In the second display mode, each data field is displayedhierarchically in a respective user-defined folder, and the user-definedfolders are distinct from the system-defined objects. The method 1200further includes receiving (1250), in either the first display mode orthe second display mode, user input in the search box 830. The userinput includes (i) a predefined contiguous string of charactersspecifying a search parameter and (ii) a search string. The method 1200also includes, in response to the user input in the search box 830 and adetermination that the search parameter specifies a first metadatacharacteristic about data fields in the data source, filtering (1260)the data fields displayed in the schema region 150, thereby displaying(1260) only data fields whose metadata characteristic includes thesearch string. An example of a user input, in the search box 830, thatincludes (i) a predefined contiguous string of characters specifying asearch parameter and (ii) a search string is provided with respect toFIG. 8N.

In some implementations, the schema region 150 includes (1232) thesearch box 830. FIG. 8N shows a schema region 150 that includes thesearch box 830.

In some implementations, the first metadata characteristic stores (1262)user-provided comments about data fields from the data source.

In some implementations, the method 1200 further includes detecting(1270) a user gesture (e.g., a hover, click, or double-click)corresponding to a first data field displayed in the schema region 150.In response to detecting the user gesture, the method displays (1272) acomment associated with the first data field. FIG. 8N shows an examplewhere in response to a user gesture (in this example, a hover) over thedata field “Isbn,” the computer displays a comment, “Certified ISBN,”which is associated with the data field “Isbn.”

The terminology used in the description of the invention herein is forthe purpose of describing particular implementations only and is notintended to be limiting of the invention. As used in the description ofthe invention and the appended claims, the singular forms “a,” “an,” and“the” are intended to include the plural forms as well, unless thecontext clearly indicates otherwise. It will also be understood that theterm “and/or” as used herein refers to and encompasses any and allpossible combinations of one or more of the associated listed items. Itwill be further understood that the terms “comprises” and/or“comprising,” when used in this specification, specify the presence ofstated features, steps, operations, elements, and/or components, but donot preclude the presence or addition of one or more other features,steps, operations, elements, components, and/or groups thereof.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific implementations. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theimplementations were chosen and described in order to best explain theprinciples of the invention and its practical applications, to therebyenable others skilled in the art to best utilize the invention andvarious implementations with various modifications as are suited to theparticular use contemplated.

What is claimed is:
 1. A method for analyzing data from data sources,comprising: at a computer system having one or more processors andmemory storing one or more programs configured for execution by the oneor more processors: receiving user selection of a data source;displaying a data visualization user interface, including a schemaregion and a search box, wherein: each data field displayed in theschema region is associated with a respective system-defined object fromthe data source; and in a first display mode, displaying the schemaregion includes hierarchically displaying each system-defined object andthe data fields associated with the respective system-defined object;receiving user input to switch from the first display mode to a seconddisplay mode in which each data field is displayed hierarchically in arespective user-defined folder, wherein the user-defined folders aredistinct from the system-defined objects; in either the first displaymode or the second display mode, receiving user input, in the searchbox, including (i) a predefined contiguous string of charactersspecifying a search parameter followed by (ii) one or more charactersspecifying a search string; and in response to the user input in thesearch box, filtering the data fields displayed in the schema region,displaying only data fields (i) whose data type matches a data typespecified by the search parameter and (ii) who displayed names includethe search string.
 2. The method of claim 1, wherein: the user inputincludes the predefined contiguous string of characters followed by oneor more characters specifying a search string; the search parameterspecifies searching for calculated data fields; and filtering the datafields displayed in the schema region further comprises displaying onlydata fields whose displayed names include the search string or whosecorresponding calculation expressions include the search string.
 3. Themethod of claim 1, wherein the data type specified by the searchparameter is one of (i) dimension, (ii) measure, or (iii) calculation.4. The method of claim 1, wherein receiving the user input in the searchbox comprises: detecting a user gesture to display a list of predefinedsearch parameters; in response to detecting the user gesture, displayingthe list of predefined search parameters; and in response to receiving auser selection from the displayed list, automatically populating thesearch box with the predefined contiguous string of characterscorresponding to the user selection from the displayed list.
 5. Themethod of claim 1, further comprising: continuing to display only datafields whose data type matches the data type specified by the searchparameter in response to receiving the user input to switch from thefirst display mode to the second display mode.
 6. The method of claim 1,wherein the schema region includes the search box.
 7. The method ofclaim 1, further comprising: receiving user selection of a data fielddisplayed in the schema region and user placement of the selected datafield into a data visualization definition region of the datavisualization user interface; generating a data visualization based onthe user selection and placement; and displaying the generated datavisualization, including one or more visual marks corresponding to datafrom the selected data field.
 8. A method for analyzing data from datasources, comprising: at a computer system having one or more processorsand memory storing one or more programs configured for execution by theone or more processors: receiving user selection of a data source;displaying a data visualization user interface, including a schemaregion and a search box, wherein: each data field displayed in theschema region is associated with a respective system-defined object fromthe data source; and in a first display mode, displaying the schemaregion includes hierarchically displaying each system-defined object andthe data fields associated with the respective system-defined object;receiving user input to switch from the first display mode to a seconddisplay mode in which each data field is displayed hierarchically in arespective user-defined folder, wherein the user-defined folders aredistinct from the system-defined objects; in either the first displaymode or the second display mode, receiving user input, in the searchbox, including (i) a predefined contiguous string of charactersspecifying a search parameter and (ii) a search string; and in responseto the user input in the search box and a determination that the searchparameter specifies a first metadata characteristic about data fields inthe data source, filtering the data fields displayed in the schemaregion, displaying only data fields whose first metadata characteristicincludes the search string.
 9. The method of claim 8, wherein the firstmetadata characteristic stores user-provided comments about data fieldsfrom the data source.
 10. The method of claim 9, further comprising:detecting a user gesture corresponding to a first data field displayedin the schema region; and in response to detecting the user gesture,displaying a comment associated with the first data field.
 11. Themethod of claim 8, wherein the schema region includes the search box.12. A computing device, comprising: one or more processors; memory; adisplay; and one or more programs stored in the memory and configuredfor execution by the one or more processors, the one or more programscomprising instructions for: receiving user selection of a data source;displaying a data visualization user interface, including a schemaregion and a search box, wherein: each data field displayed in theschema region is associated with a respective system-defined object fromthe data source; and in a first display mode, displaying the schemaregion includes hierarchically displaying each system-defined object andthe data fields associated with the respective system-defined object;receiving user input to switch from the first display mode to a seconddisplay mode in which each data field is displayed hierarchically in arespective user-defined folder, wherein the user-defined folders aredistinct from the system-defined objects; in either the first displaymode or the second display mode, receiving user input, in the searchbox, including (i) a predefined contiguous string of charactersspecifying a search parameter followed by (ii) one or more charactersspecifying a search string; and in response to the user input in thesearch box, filtering the data fields displayed in the schema region,displaying only data fields (i) whose data type matches a data typespecified by the search parameter and (ii) who displayed names includethe search string.
 13. The computing device of claim 12, wherein: theuser input includes the predefined contiguous string of charactersfollowed by one or more characters specifying a search string; thesearch parameter specifies searching for calculated data fields; andfiltering the data fields displayed in the schema region furthercomprises displaying only data fields whose displayed names include thesearch string or whose corresponding calculation expressions include thesearch string.
 14. The computing device of claim 12, wherein the datatype specified by the search parameter is one of (i) dimension, (ii)measure, or (iii) calculation.
 15. The computing device of claim 12,wherein receiving the user input in the search box comprises: detectinga user gesture to display a list of predefined search parameters; inresponse to detecting the user gesture, displaying the list ofpredefined search parameters; and in response to receiving a userselection from the displayed list, automatically populating the searchbox with the predefined contiguous string of characters corresponding tothe user selection from the displayed list.
 16. The computing device ofclaim 12, the one or more programs further comprising instructions for:continuing to display only data fields whose data type matches the datatype specified by the search parameter in response to receiving the userinput to switch from the first display mode to the second display mode.17. The computing device of claim 12, wherein the schema region includesthe search box.
 18. The computing device of claim 12, the one or moreprograms further comprising instructions for: receiving user selectionof a data field displayed in the schema region and user placement of theselected data field into a data visualization definition region of thedata visualization user interface; generating a data visualization basedon the user selection and placement; and displaying the generated datavisualization, including one or more visual marks corresponding to datafrom the selected data field.